CrawlCheck

Agent view · Findings · 2026-11-13

A slider that took 8.8 seconds: three 328 KB PNGs

This is the response this server returns to a client that asks for Accept: text/markdown at https://crawlcheck.io/blog/a-slider-that-took-8-seconds-three-328-kb-pngs: fetched when you opened this page, shown byte for byte. An assistant, a crawler that negotiates markdown, or anything reading our feed gets exactly this. The markdown leaves signed (RFC 9421, key in our key directory), so a crawler can prove the page it read is the page this server sent; the check is shown below.

status200
content-typetext/markdown; charset=utf-8
varyAccept
link<https://crawlcheck.io/llms.txt>; rel="describedby"; type="text/plain", <https://crawlcheck.io/.well-known/api-catalog>; rel="service-desc"; type="application/linkset+json", <https://crawlcheck.io/blog/a-slider-that-took-8-seconds-three-328-kb-pngs>; rel="cite-as", <https://crawlcheck.io/.well-known/http-message-signatures-directory>; rel="http-message-signatures-directory"
cache-controlpublic, max-age=900, stale-while-revalidate=2400
bytes11,346
words1,619
sha-2568271b16b034955200a7759f9640cf7b99a6f09094b6ee027a0f96a556404307d
repr-digestsha-256=:gnGxawNJVSAKd1n5ZAz3uZpvCQlLbuAnoPlqVWQEMH0=: ← matches the body shown
signature-inputsig1=("@authority";req "@path";req "repr-digest" "content-type");created=1795180564;expires=1795184164;keyid="1hHmE3fo1rg5Ig70wuFtJ5wBc7G-sUTgUJkxyPWFRps";alg="ed25519";nonce="190DWUi46euMSS3uu6FVDg";tag="crawlcheck-page"
signaturesig1=:Vk197E8hfrdw49GHtkwmEggJkJAO6dyuCSqC7XDDAJUNBjgYTx9ZT/N6cPtz2QjC3KyT/7xilt0zNL/4tOPCAQ==:
verifiedyes — signature by key 1hHmE3fo1rg5Ig70… from https://crawlcheck.io/.well-known/http-message-signatures-directory (directory valid), valid for 3600 more s. Checked here exactly as a crawler would; redo it yourself: https://crawlcheck.io/api/tool/wba
Findings · 2026-11-13 · By [VSNARY | Emmanuel Orta](/author)

# A slider that took 8.8 seconds: three 328 KB PNGs

A home page slider on a site we run held the main image back for almost nine seconds in a lab test. Three ordinary causes, three fixes, and the numbers after each.

On a service site we run, the home page slider's first image took 8.8 seconds to appear in a Lighthouse test on a simulated slow phone connection. Three causes added up: the first slide waited for the whole page to finish loading, three font files loaded one after another and blocked rendering, and the three slides were PNG files of 322 to 328 KB each. After fixing all three the same test read 2.1 seconds and the performance score went from 0.66 to 0.98.

On this page

- The readings
- Cause one: the slide waited for everything else
- Cause two: fonts in a chain
- Cause three: the images themselves
- What to take from it

Paint times, start of day and after the fixes
Largest image painted, start of day 8.8 s

Largest image painted, after 2.1 s

First content painted, start of day 4.0 s

First content painted, after 1.7 s

This is a case from one of our own sites, a local service business with a theme-built slider at the top of its home page. The numbers are lab numbers: [Lighthouse](/glossary/lighthouse), simulated slow 4G, run by us on 13 November 2026. Real visitors on fast connections saw less delay, and [field data](/glossary/field-data) will take weeks to reflect the change.

## The readings #

| Measure | Start of day | After the fixes |
| --- | --- | --- |
| Largest image painted ([LCP](/glossary/lcp)) | 8.8 s | 2.1 s |
| First content painted (FCP) | 4.0 s | 1.7 s |
| Layout shift ([CLS](/glossary/cls)) | 0.233 | 0.019 |
| Lighthouse performance score | 0.66 | 0.98 |
| Render-blocking files in the head | 33 | 4 |

## Cause one: the slide waited for everything else #

The slider script only revealed the first slide once the whole page had finished loading. So the largest thing on the screen was the last thing to appear, however fast it downloaded. We made the first slide part of the first paint and let the script take over afterwards. Layout shift dropped to zero in the same step, because the space was no longer empty and then filled.

## Cause two: fonts in a chain #

The theme's stylesheet imported three web font files, each from inside the one before. A browser cannot start the second until it has read the first, and nothing renders while it waits. Serving the three as one file took first paint from 4.0 to 1.7 seconds and the slide from 8.8 to 6.5.

## Cause three: the images themselves #

The three slides were PNG files of 322 to 328 KB each. PNG is the wrong format for photographs. As WebP the same slides are 22, 16 and 14 KB, with transparency kept where two of them used it. That took the slide from 6.5 to 2.1 seconds.

## What to take from it #

None of the three causes is unusual, and no single one explains the result. Check them in this order on your own page: is the main image waiting on a script, is anything in the head loading in a chain, and is the image in a format that suits it. The order matters because the first two cost nothing to fix in bytes. For why one lab run is not a verdict, see [our note on Lighthouse](/blog/one-lighthouse-run-cannot-support-a-finding-225-percent-variance).

CrawlCheck’s dataset when this page loaded: 570,959 sites measured.

Written by

[Emmanuel Orta](/author) · VSNARY

I build CrawlCheck and write everything published here, from measurements the verification layer took. Where a post got something wrong, the correction stays in the post.

[Every post, and where I got it wrong →](/author) · [Follow on LinkedIn →](https://www.linkedin.com/in/emmanuelorta)

Share this finding: [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fa-slider-that-took-8-seconds-three-328-kb-pngs%3Futm_source%3Dlinkedin%26utm_medium%3Dsocial%26utm_campaign%3Dshare)[X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fa-slider-that-took-8-seconds-three-328-kb-pngs%3Futm_source%3Dx%26utm_medium%3Dsocial%26utm_campaign%3Dshare&text=A%20slider%20that%20took%208.8%20seconds%3A%20three%20328%20KB%20PNGs)[Email](mailto:?subject=A%20slider%20that%20took%208.8%20seconds%3A%20three%20328%20KB%20PNGs&body=https%3A%2F%2Fcrawlcheck.io%2Fblog%2Fa-slider-that-took-8-seconds-three-328-kb-pngs)[Follow Emmanuel on LinkedIn](https://www.linkedin.com/in/emmanuelorta)

## Questions this post answers

### Why was the slider image so slow to appear?

Three things added up: the script showed the first slide only after the whole page loaded, three font files loaded in a chain and blocked rendering, and the slides were PNG files of about 325 KB each.

### How much did converting PNG to WebP save?

Each slide went from 322 to 328 KB down to 22, 16 and 14 KB, and the lab reading for the largest image went from 6.5 to 2.1 seconds.

### Are these real visitor numbers?

No. They are Lighthouse lab readings on a simulated slow 4G connection, taken on 13 November 2026. Field data from real visitors takes weeks to reflect a change.

### Which fix should I try first?

Make sure the main image is not waiting on a script, then remove chained files from the head, then fix the image format. The first two need no new files.

## Related findings

[2026-11-18 The quote form was the slow part: 980 ms cut to 50 ms A home page froze for 980 ms on load. 16 of the 18 slow tasks were the quote form and its captcha. Loading the form on first touch](/blog/the-quote-form-was-the-slow-part-980-ms-to-50)[2026-09-01 Page builders drop the main landmark: nine HTML checks Page builders can silently drop the main landmark a screen reader jumps to. Nine structure checks you can run on the HTML your ser](/blog/accessibility-structure-nine-things-a-screen-reader-needs-before-contrast-matters)[2026-08-26 Lighthouse scores vary between runs: two runs, 225% apart Two Lighthouse runs of an unchanged page, minutes apart: blocking time 2,643 ms then 812 ms. How to find your noise floor before a](/blog/one-lighthouse-run-cannot-support-a-finding-225-percent-variance)

The main product

Found this on your own site? **We fix it for $100.**

Scan free to see where you stand. The fix is one site, every finding implemented and re-measured, with a sealed before and after.

[Fix it all — $100](https://buy.stripe.com/4gM00j7OjawhdLEdyR2VG0v)
[What it covers](/pricing#fix) · [scan first, it is free](/)

Free browser extension

Check this on any site you open, **without leaving the page.**

CrawlCheck for Chrome grades every site you visit A–F and shows, from your own browser, what search engines and AI assistants are actually served. Free, no account.

[Add to Chrome — free](https://chromewebstore.google.com/detail/plgjengobhbdmbgckiiaaflgiepdbcpi?utm_source=crawlcheck.io&utm_medium=post)
[What it does](/extension)

Write for the library

Measured something yourself? **Submit an article.**

Send your finding, the data and the method. A person reads every submission and replies by email; accepted articles are published under your name with a link to your study. Free to submit. Articles are accepted on merit; no one can pay to have one published.

[Submit an article](/submit-finding#send)
[How it works](/submit-finding) · a reply within about a week

Spotted a mistake or a bug on this page? [Report an error](/report-error?k=article). Confirmed errors are fixed and logged on the [corrections page](/corrections).

## Comments

Comments are read before they appear. Nothing is published automatically, and no account is needed. An AI agent with a published signing key can post without the queue: it signs the request and the signature is checked against its own domain ([how](/api/comment/signed)). Those appear at once, marked *verified*.

Send for review

Writing about this? [Facts, live figures and marks](/press) — every number on that page is dated and traceable to a scan.

[All findings](/blog) · [The dataset](/data) · [How the dataset works](/policy)

We read your site the way crawlers do, from our own network, and every report says exactly what was asked for and what came back. [Who runs this](/author) · [Press kit](/press) · [Videos](/videos) · [Evidence for disputes](/evidence) · [YouTube](https://www.youtube.com/@crawlcheck) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io)

#### How we measure, and our own machine files

CrawlCheck reads every site as itself. Its crawler-identity tests send named user-agent strings from its own network, never from an operator’s published range, so a site that verifies crawlers can tell them apart; every report says so. Results reflect what an anonymous non-browser client receives. [What we collect and how to opt out](/policy) · [how every report is timestamped](/proof) · [who runs this](/author) · [press kit](/press) · [hello@crawlcheck.io](mailto:hello@crawlcheck.io).

**Second vantage:** the [browser extension](/extension) measures what crawlers are served from your own address and after your JavaScript runs — the half this server cannot see. From 1.0.0 it sends the domain you ask about, on one button, and anonymous usage counts you can switch off; from 1.0.3 a footer switch turns off the hostname lookup for the grade on the icon; from 1.0.4 a share switch, on by default, sends a signed Two-vantages reading (status, size, words and a hash per identity; never page text); from 1.0.16 chips send the hostnames of search results and AI citations while the chips and grade switches are on; from 1.0.17 a readings switch, on by default, sends one signed page reading a day (numbers, the hostname and the page address with the query removed; never in incognito; at most 40 a day) and only while the share and grade switches are also on. Earlier versions send nothing.

**Our own machine layer for the agentic web:** [llms.txt](/llms.txt) · [llms-full.txt](/llms-full.txt) · [agents.md](/agents.md) · [SKILL.md](/SKILL.md) · [entitymap.json](/entitymap.json) · [media kit](/.well-known/media-kit.json) · [MCP server card](/.well-known/mcp/server-card.json) · [API catalog](/.well-known/api-catalog) · [OpenAPI](/openapi.json) · [robots.txt](/robots.txt) · [sitemap.xml](/sitemap.xml) · [security.txt](/.well-known/security.txt) — every one named in robots.txt, which is exactly what we check for on yours.

**Registry:** [MCP](/registry/mcp) · [AI policy](/registry/aipolicy) · [Place: Vancouver](/registry/place/bc/vancouver) | **Pages:** [IP ranges](/data/ip-ranges) · [Keys](/keys) · [Cloudflare](/fix/cloudflare) · [Visitor resolve](/spec/visitor-resolve) | **Datasets:** [Oklahoma](/datasets/state/oklahoma) · [Technologies: Jquery](/datasets/technologies/jquery) · [Problems: Declared sitemap broken](/datasets/problems/declared-sitemap-broken) | **Blog:** [A slider that took 8.8 seconds: three 328 KB PNGs](/blog/a-slider-that-took-8-seconds-three-328-kb-pngs) | **Glossary:** [agentic knowledge graph](/glossary/agentic-knowledge-graph)

[Contact](/contact) · [Partnerships](/partnerships) · [Terms of service](/terms) · [Refund policy](/refunds) · [Trust center](/trust) · [Subprocessors](/subprocessors) · [Changelog](/changelog) · [Report an error](/report-error)

Same body as a file: /blog/a-slider-that-took-8-seconds-three-328-kb-pngs.md · as data: /feed.json · what we tell agents site-wide: /llms.txt, /agents.md. To see any other site this way, from your own browser, after its JavaScript runs: the browser extension.