Your weekly report
A complete report for a fictitious bakery, presented exactly as you would receive it. In a real report, every score comes directly from Google’s test of your website.
How to read this report
Sample data
Website health report
example-bakery.es
Tested on 26 October 2026
Your website is slow on mobile and needs improvement on desktop.
On mobile, the main content took 4.7 seconds to appear in Google’s test, which is slow. On desktop it appeared after 1.6 seconds, but the desktop speed score still needs improvement. On both devices, Google found oversized images and files that delay the page. Google can read your page well, and the website follows current security standards, so the priority is mobile speed.
Since the previous check
Compared with the check on 19 October 2026.
- Mobile speed39 → 41 · recent results 39–44No clear change
- Desktop speed70 → 72 · recent results 70–74No clear change
- Accessibility (mobile)61 → 67 · +6 points (+10%)Better
- Accessibility (desktop)66 → 71 · +5 points (+8%)Better
All other scores: no change.
Fixed since the previous check
- Images without a description
New since the previous check
- Text that is hard to read against its background
Google’s speed score varies from test to test, even when nothing on the page changes, so speed only counts as better or worse when it is at least 10 points outside your recent results. Problems are compared for accessibility, search and security, where Google’s test gives the same result every time.
Health scores
Each score is out of 100 and comes directly from Google’s test.
Mobile speed
How quickly the page loads on a mobile phone. The main content appeared after 4.7 s in Google’s test.
41 / 100
PoorDesktop speed
How quickly the page loads on a laptop or desktop computer. The main content appeared after 1.6 s in Google’s test.
72 / 100
Needs improvementAccessibility
Whether people with impaired vision, or who use screen readers, can read and use the page. Mobile 67, desktop 71 (lower score shown).
67 / 100
Needs improvementSearch engine readiness
The technical basics Google needs to read and list your page. This is not your ranking. Same on mobile and desktop.
92 / 100
GoodSecurity and best practice
Whether the website follows current security and web standards. Same on mobile and desktop.
100 / 100
Good
Recommended actions
- 1
Compress your images
High priorityNo developer neededMobile and desktopOversized photographs take longer to download, so visitors wait longer for the page to appear, especially on mobile.
Recommended action: Resize each photograph to the size at which it is displayed, and save it as a compressed JPG or WebP file before uploading. Many website builders can do this automatically.
Google’s findings
- Oversized imagesMobile: a potential saving of about 1.9 MB (Google’s estimate). Desktop: a potential saving of about 0.8 MB (Google’s estimate).
- 2
Defer files that delay the page
Medium priorityDeveloper neededMobile and desktopSeveral code and style files must load before any content appears, so visitors see a blank screen for longer.
Recommended action: Ask your web developer to load these files later, or only on the pages that require them.
Google’s findings
- Files that delay the pageMobile: a potential saving of about 1.2 s (Google’s estimate). Desktop: a potential saving of about 0.4 s (Google’s estimate).
- 3
Use descriptive link text
Low priorityNo developer neededMobile and desktopLinks such as “click here” or “read more” do not tell visitors, or Google, where they lead.
Recommended action: Replace them with text that describes the destination, for example “View our cake menu”.
Google’s findings
- Links without descriptive textMobile and desktop: 4 found.
Real visitor data
Real visitors on mobile (entire website): responsiveness and visual stability are good; loading speed needs improvement.
On mobile (entire website)
- Loading speed2.6 sNeeds improvement
- Responsiveness120 msGood
- Visual stability0.02Good
Based on real Chrome users over the past 28 days.
Other observations
- Some light grey text on a white background is difficult for some visitors to read.
- On mobile, several buttons are placed close together, which makes accidental taps more likely.
Technical details (for developers)
| Measurement | Mobile | Desktop |
|---|---|---|
| Main content displayed (LCP) | 4.7 s | 1.6 s |
| First content displayed (FCP) | 2.1 s | 0.7 s |
| Total blocking time (TBT) | 380 ms | 90 ms |
| Layout shift (CLS) | 0.02 | 0.01 |
| Speed index | 5.2 s | 1.8 s |
Measured in Google’s simulated test, not by real visitors.
Next scheduled test: around 2 November 2026
This report covers one page (https://example-bakery.es/) and is based on Google PageSpeed Insights. Scores can vary slightly between tests, so small differences are normal. The report identifies issues; it does not guarantee any change in Google rankings.
Start monitoring your website
Setup takes a few minutes, and your first report is usually ready within an hour.