Sample report, demo website

Speed and SEO audit: Høstlys Coffee Roasters

This is the kind of report you get with my audit service. It was made for the "before" version of a fictional website, and the fixes it recommends were then applied to produce the "after" version.

Page auditedpage-speed-demo/before/

Measured11 October 2026

ToolGoogle PageSpeed Insights, mobile

Prepared byIvan

Summary

On a typical phone the page needs 26.6 s to show its main image, and the visitor sees a blank screen for the first 3.3 s. Almost all of the delay comes from two things: photos that are far larger than they need to be, and files that the browser must download before it can show anything.

Below are six fixes, ordered by impact. The first two give most of the gain. None of them need a redesign or a new platform, and the page will look the same to visitors.

Mobile result	Now	After the fixes
Performance score (0–100)	66	97
Main content visible (LCP)	26.6 s	2.4 s
First content visible (FCP)	3.3 s	0.8 s
Page weight	4.8 MB	34 KB
Accessibility score	85	100
SEO score	91	100

Google considers LCP under 2.5 s good and over 4 s poor. Lab results vary a little between runs.

Findings and fixes

1. Photos are 10 to 20 times larger than needed

High impact

Found: Four JPEG photos, 4000 and 2400 px wide, 4.6 MB together. On a phone they are shown about 350 to 400 px wide.
Why it matters: The main image alone is 2 MB, which is why it takes 26.6 s to appear on a mobile connection.
Fix: Resize to the displayed size (and double for sharp screens), serve AVIF with a WebP fallback, let the browser choose the size with srcset, and lazy-load images below the first screen.
Effort: 1–2 hours

2. Six files block the first paint

High impact

Found: Bootstrap CSS and JavaScript, Font Awesome, jQuery and three font families load in the <head> before anything is shown. PageSpeed estimates 2.8 s of savings. The page uses almost none of this code.
Why it matters: The visitor looks at a blank screen while these files download.
Fix: Remove the unused libraries, inline the page's own CSS (about 2.5 KB), replace the icon font with three inline SVG icons, and replace the jQuery smooth scrolling with one line of CSS.
Effort: 2–3 hours

3. Fonts: three families, fifteen weights

Medium impact

Found: Poppins in nine weights, Playfair Display and Roboto are requested, but the page uses one family in two weights. Text stays invisible until the fonts arrive.
Fix: Load only Poppins 400 and 600 with font-display: swap, without blocking rendering, so the text is visible immediately.
Effort: 30 minutes

4. Content jumps while loading

Medium impact

Found: Images have no width and height, and a promo bar is inserted by a script one second after load, pushing the whole page down.
Why it matters: Visitors lose their place or tap the wrong thing. Layout shift (CLS) is one of Google's Core Web Vitals.
Fix: Set image dimensions and put the promo bar in the HTML from the start.
Effort: 30 minutes

5. Accessibility and SEO basics

Low effort

Found: White text on the orange promo bar does not have enough contrast, a heading level is skipped, there is no main landmark, and the page has no meta description.
Fix: Darken the promo colour slightly, fix the heading order, wrap the content in <main>, and write a meta description for search results.
Effort: 30 minutes

6. Short cache lifetime

Depends on hosting

Found: Static files are cached for only 10 minutes, so returning visitors download them again.
Fix: On most hosts: cache images, CSS and fonts for a year and change file names when they change. On this demo host (GitHub Pages) the cache time cannot be configured, so this item stays open.
Effort: 15–30 minutes, if the host allows it

What this report does not cover

Real-visitor speed data from Google (the Chrome User Experience Report) is only available for sites with enough traffic, so this audit uses lab measurements. After the fixes go live, I re-run the same measurements to confirm the result.