Sample report
SEO audit report example: tesvotech.com
This is a real Serpzeno audit of tesvotech.com, the website of Tesvo Technologies (the company behind Serpzeno), run on 19 November 2026. Nothing was edited: it shows exactly what your own report contains.
Grades by category
- On-pageA98/1007 passed · 2 warnings · 1 failed
- ContentA100/1003 passed · 0 warnings · 0 failed
- TechnicalA100/1009 passed · 0 warnings · 0 failed
- PerformanceA95/1003 passed · 1 warnings · 0 failed
- SecurityA100/1001 passed · 0 warnings · 0 failed

What the audit found, and how to fix it
Problems are ranked by impact. In the app each one lists the affected pages and comes with an AI-written fix; here we summarise them.
- High
Two service pages have almost the same title (82% alike)
Where: /services/mobile-app-development and /services/flutter-app-development
“Mobile App Development for iOS and Android | Tesvo” and “Flutter App Development for iOS and Android | Tesvo”. When titles are this close, Google can treat the pages as competing for the same searches and show neither well.
How to fix: Make each title describe what is different about the page: lead the Flutter page with “Flutter” and the framework benefit, and give the general mobile page its own angle (native and React Native, for example).
- Warning
Layout shifts while the page loads (CLS 0.215)
Where: Home page (lab test)
Cumulative Layout Shift measures how much the page jumps as it loads. 0.215 is above Google’s 0.1 target for a good experience, even though overall performance scores 100.
How to fix: Give images, embeds and late-loading blocks a fixed width and height (or aspect ratio), and avoid inserting banners above content after the first paint.
- Warning
Blog index meta description is short (113 characters)
Where: /blog
Short descriptions waste space in search results, where a clear 120–160 character summary earns more clicks.
How to fix: Write a description of 120–160 characters that says what readers will find, for example the topics the blog covers.
- Low
Images not in WebP on 10 blog pages
Where: /blog and 9 articles
Most images on these pages are PNG or JPEG. WebP files are usually 25–35% smaller, which helps load time on mobile.
How to fix: Serve article covers and inline images as WebP (keeping a fallback only if old browsers matter).
All 28 checks
“Pages” shows how many pages had the problem out of the pages the check applies to. Core Web Vitals from real users didn't run because Google doesn't yet have enough Chrome visits for this site.
On-page
| Check | Result | Pages |
|---|---|---|
| Title tagEvery page has a title tag. | Passed | 0 / 38 |
| Title lengthTitles are 30–60 characters, so they show in full in search results. | Passed | 0 / 38 |
| Unique titlesNo two pages share the same title. | Failed | 2 / 38 |
| Meta descriptionEvery page has a meta description. | Passed | 0 / 38 |
| Meta description lengthDescriptions are 120–160 characters. | Warning | 1 / 38 |
| Unique meta descriptionsNo two pages share the same description. | Passed | 0 / 38 |
| H1 headingEvery page has a main H1 heading. | Passed | 0 / 38 |
| Image alt textImages have alt text for search engines and screen readers. | Warning | 10 / 38 |
| Open Graph tagsPages have og:title, og:description and og:image for social sharing. | Passed | 0 / 38 |
| Structured dataPages include schema.org markup. | Passed | 0 / 38 |
Content
| Check | Result | Pages |
|---|---|---|
| Content lengthPages have at least 300 words. | Passed | 0 / 38 |
| Duplicate contentPages don’t repeat each other’s content. | Passed | 0 / 38 |
| Content structurePages use H2 subheadings to organize content. | Passed | 0 / 38 |
Technical
| Check | Result | Pages |
|---|---|---|
| Indexable pagesPages aren’t blocked from Google by noindex or robots rules. | Passed | 0 / 38 |
| Canonical tagsPages declare a correct canonical URL. | Passed | 0 / 38 |
| Unique canonicalsDifferent pages don’t claim the same canonical URL. | Passed | 0 / 38 |
| Internal linksPages link to other pages on the site. | Passed | 0 / 38 |
| Orphan pagesEvery page is linked from somewhere else on the site. | Passed | 0 / 38 |
| Broken linksLinks on the homepage work. | Passed | 0 / 1 |
| hreflang tagsLanguage versions point to each other correctly. | Passed | 0 / 38 |
| XML sitemapThe site has a sitemap.xml. | Passed | 0 / 1 |
| robots.txtThe site has a robots.txt file. | Passed | 0 / 1 |
Performance
| Check | Result | Pages |
|---|---|---|
| PageSpeed scoreGoogle’s Lighthouse performance score is 90 or higher. | Passed | 0 / 1 |
| Core Web Vitals (real users)Real Chrome users get fast loading, quick responses and a stable layout. | Not run | – |
| Largest Contentful PaintThe main content appears within 2.5 seconds. | Passed | 0 / 1 |
| Layout stability (CLS)The page doesn’t jump around while it loads (CLS 0.1 or less). | Warning | 1 / 1 |
| Total Blocking TimeScripts block the page for 200 ms or less. | Passed | 0 / 1 |
Security
| Check | Result | Pages |
|---|---|---|
| SSL certificateThe site has a valid HTTPS certificate. | Passed | 0 / 1 |
Speed and technical details
- Lighthouse performance
- 100/100
- Largest Contentful Paint
- 0.36 s
- First Contentful Paint
- 0.28 s
- Total Blocking Time
- 38 ms
- Layout shift (CLS)
- 0.215
- Speed Index
- 0.73 s
- URLs in sitemap.xml
- 38
- robots.txt
- Found, crawling allowed
- SSL certificate
- Valid, 82 days left
Get this report for your own website
The Free plan audits one website every week, with no credit card. Paid plans add more websites, daily rank tracking and PDF export. Read more about the SEO audit.
Audit my website free