Full website audit
One run — a complete technical diagnosis: performance, accessibility, SEO, security and an AI assessment of the interface. A detailed report with screenshots and plain-language recommendations for every page.
What you get
Not just “up / down”, but a full picture of your site's health
Dozens of checks in one run
Speed, Lighthouse, accessibility, SEO, security, layout and indexing — all in one report, with no manual tool setup.
AI interface perception
The model looks at page screenshots like a user and rates clarity, visual hierarchy, copy and usability — with concrete recommendations.
A clear report
A score per section, screenshots of every crawled page and plain-language recommendations. Export to PDF for a client or your team.
All checks in the full audit
The complete list of items that go into the report for every page
Technical parameters
| Secure connection (HTTPS) | The site loads over a secure protocol — data between the browser and server is encrypted. |
| SSL certificate expiry | Days left until the SSL certificate expires. Once expired, the browser shows a security warning. |
| Security headers (HSTS, CSP, X-CTO) | Security HTTP headers (HSTS, CSP, X-Content-Type-Options) protect against several common attacks. |
| Mixed (insecure) content | Loading insecure (http) files on a secure (https) page — lowers security and browser trust. |
| HTTP → HTTPS redirect | Opening the site over http automatically redirects to secure https. |
| www / non-www canonicalization | The www and non-www versions lead to one. Otherwise search engines treat them as different sites and split ranking. |
| Custom 404 page | A non-existent URL shows a meaningful 404 page with navigation, not a blank error. |
| Response compression (gzip/brotli) | The server response is compressed (gzip or brotli) — the page is transferred smaller and loads faster. |
| JavaScript errors | JavaScript errors in the browser console — can break functionality and interactive elements. |
| Broken links | Links pointing to non-existent pages (404/5xx errors). Frustrate users and hurt SEO. |
| Failed resources | Images, scripts or styles that failed to load when the page opened. |
| robots.txt | The robots.txt file tells search engines which pages may be indexed and which may not. |
| sitemap.xml | The sitemap.xml helps search engines quickly discover all pages of the site. |
Speed & health
| Lighthouse Performance | Overall page speed score from Google Lighthouse on a 0–100 scale. |
| LCP (largest contentful paint) | Largest Contentful Paint — how long the main content takes to render. Good is under 2.5 s, poor is over 4 s. |
| TTFB (time to first byte) | Time To First Byte — how long the server takes to start responding. Good is under 0.8 s. |
| CLS (layout shift) | Cumulative Layout Shift — how much the layout "jumps" during loading (content shifting under a button you already tapped). Good is under 0.1. |
| Page weight | Total size of all page files. The heavier it is, the longer it loads, especially on mobile. |
| Request count | How many separate files the page requests. A large number of requests slows loading. |
| Image optimization | Images are compressed and in modern formats (WebP/AVIF) — saves traffic and speeds up loading. |
| Unused CSS/JS | Share of the loaded CSS and JS not used while rendering the page («dead weight»). The lower it is, the faster the page loads and the less traffic it uses. |
SEO & content meta
| <title> tag | The page title in search results and the browser tab. Optimal length is 10–70 characters. |
| Meta description | The short summary under the title in search results. Optimal length is 50–160 characters. |
| H1 heading | The main visible heading of the page. There should be exactly one H1 per page. |
| Canonical | The canonical tag tells search engines the primary URL of a page — prevents duplicate listings. |
| Open Graph markup | Open Graph tags define how the page looks when shared on social media and messengers (image, title, description). |
| Favicon | The small site icon shown in the browser tab and bookmarks. |
| lang attribute | The page language is set (lang attribute) — important for search engines and screen readers. |
| Schema.org markup present | The page has Schema.org markup (JSON-LD) — search engines understand the content (products, reviews, organization) and can show a rich snippet. Checks presence only. |
| Microdata correctness | Separately from presence — the quality of the markup that is already there: the JSON-LD is not broken and the required type fields are filled in. Without this a rich snippet will not appear even when markup exists. If there is no markup, this item is not scored. |
| Image alt attributes | Share of images with a text description (alt) — needed for blind users and for SEO. |
| Duplicate title / description | Identical title or description across different pages — hurts search ranking. |
| hreflang (language versions) | hreflang tags tell search engines the language/region versions of a page. |
Accessibility (WCAG)
| Lighthouse Accessibility | Accessibility score from Google Lighthouse on a 0–100 scale. |
| axe / WCAG issues | Number of accessibility (WCAG) issues found by the automated axe scanner. |
| Text contrast | Sufficient contrast between text and background — text stays readable, including for low-vision users. |
| Form field labels | Form fields have labels. Without them it is unclear what to enter, and fields are inaccessible to screen readers. |
Responsiveness
| Meta viewport | The viewport meta tag. Without it the site does not adapt to phone screen width. |
| No horizontal scroll | No horizontal scrolling on mobile — all content fits the screen width. |
| Tap target size | Buttons and links are large and spaced enough to tap comfortably with a finger. |
| Font legibility | Font size is large enough for comfortable reading on a phone without zooming. |
| Content within viewport | Content does not extend beyond the screen edges on a mobile device. |
Analytics
| Analytics counters | Whether web-analytics counters (Google Analytics, Plausible, Yandex.Metrica, etc.) are installed to track visits. |
| Cookie consent banner | A cookie consent banner is present — a legal requirement in a number of countries. |
Perception & content (AI)
| Above-the-fold clarity | Whether it is clear from the first screen what the site is and what it offers (AI assessment from screenshot). |
| Usability heuristics (Nielsen) | Compliance with basic usability principles (Jakob Nielsen heuristics), AI assessment. |
| Copywriting quality | Quality, clarity and persuasiveness of the page copy (AI assessment). |
| Visual hierarchy | Whether visual emphasis is set — is it clear what is primary and what is secondary (AI assessment). |
Run a full audit of your site
Just enter a URL — we'll handle the rest