8examples.com scan from 9/10/2026, 12:39:24 AM

On September 10, 2026 the Site Spider crawled 48 pages and 777 assets of 8examples.com, starting from https://8examples.com/. It scored 96 out of 100, an excellent result. 1 of 13 checks found something to fix, led by heavy assets (6); 12 checks passed. The list below shows each check's result, and the fix plan, when present, explains what to do first.

Pages crawled

48

Assets fetched

777

Status

Completed

Checks with issues

1 of 13

• Title tagsOK
  0 of 47 pages have title issues. 1 noindex or canonicalized page excluded.
• Meta descriptionsOK
  0 of 47 pages have meta description issues. 1 noindex or canonicalized page excluded.
• HeadingsOK
  0 of 47 pages have heading issues. 1 noindex or canonicalized page excluded.
• Broken linksOK
  0 internal links point at 0 broken URLs.
• RedirectsOK
  0 redirecting URLs, 0 of them chained.
• Non-200 responsesOK
  2 URLs did not return a 2xx response.
• IndexabilityOK
  0 of 47 indexable pages have indexability warnings. 1 page noindex by design.
• Image alt textOK
  0 of 121 image references have no alt attribute. 33 use an empty alt (decorative), which is fine.
• Heavy assets6 issues
  8 assets larger than 500 KB among the 100 heaviest.
• Orphan pagesOK
  0 pages have no internal links pointing at them.
• Sitemap coverageOK
  1 sitemap listing 47 URLs: 0 crawled pages missing, 0 listed URLs broken or redirecting, 0 reachable only via the sitemap.
• Thin contentOK
  0 of 47 pages have fewer than 200 words. 1 noindex or canonicalized page excluded.
• Duplicate contentOK
  0 groups of pages with identical HTML.

Your website has a great health score, but there are some issues with non-200 responses and heavy assets that need to be addressed for better performance.

1. 1

   Fix Non-200 Responses

   Why: 404 and 502 errors can harm user experience and crawlability.

   How: Remove or correct links to the URLs generating 404 and 502 errors: https://8examples.com/_next/static/chunks/%23noise and https://8examples.com/_next/image?url=%2F_next%2Fstatic%2Fmedia%2Fdashboard.46852074.jpg.

   Checks: status-codes

2. 2

   Optimize Heavy Assets

   Why: Large assets can slow down page load times, affecting user experience and SEO.

   How: Consider compressing or resizing images and videos. E.g., use tools like TinyPNG for images and HandBrake for videos to reduce their sizes.

   Checks: heavy-assets

3. 3

   Implement Lazy Loading for Images

   Why: Improves initial load time by only loading images when they are needed.

   How: Add loading='lazy' attribute to <img> tags for larger assets.

   Checks: heavy-assets

4. 4

   Consider Using Content Delivery Network (CDN)

   Why: A CDN can improve the loading time of large assets by delivering them from locations closer to users.

   How: Choose a CDN provider (like Cloudflare or Amazon CloudFront) and set it up to cache and serve your static assets.

   Checks: heavy-assets

Generated automatically; verify each change against your own site before relying on it.