whiterabbitprojects.com website review

• Reduce unused JavaScript

  2.7 s · 500 KiB

  About 500 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.7 s faster on a phone.

• Mobile performance score: 59

  59/100

  Your mobile performance score is 59 (desktop: 86). Pages that score under 90 lose visitors before the first paint.

• Render-blocking requests

  900 ms

  2 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

• Google Tag Manager adds 182 ms

  182 ms

  Google Tag Manager costs a phone 182 ms of main-thread work and 300 KiB of downloads while your page loads. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

• 6 third-party services on the page

  6 third-party services load with your homepage (Google Tag Manager, iubenda and JSDelivr CDN and others), adding 639 KiB and 299 ms of main-thread time.

• Font display

  150 ms

  Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 150 ms).

• Legacy JavaScript

  100 ms · 44 KiB

  Polyfills for old browsers add 44 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

• 4 long tasks on the main thread

  4 long tasks block the main thread while loading, the longest for 125 ms. During a long task the page ignores taps.

• Use efficient cache lifetimes

  19 KiB

  4 files are served with short cache lifetimes, so returning visitors download them again (19 KiB).

• Improve image delivery

  16 KiB

  1 image could be 16 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  Show on pageElements (1)

• Phones get a much slower page than desktops

  Desktop scores 86 but mobile only 59. A gap that wide usually means heavy scripts and images that hit phones hardest.

• Chained critical requests

  Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

• Largest Contentful Paint: 10.4 s

  10.4 s

  Your largest element takes 10.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PROJECTS”.

  Show on pageElements (1)

• First Contentful Paint: 5.7 s

  5.7 s

  The first text or image appears after 5.7 s on a phone. Good is under 1.8 s.

• Time to Interactive: 10.4 s

  10.4 s

  The page becomes fully interactive after 10.4 s. Good is under 3.8 s.

• Speed Index: 6.3 s

  6.3 s

  Visually, the page fills in at 6.3 s (Speed Index). Good is under 3.4 s.

• Largest content (LCP) got 32% slower for real visitors

  +32%

  Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Tap response (INP) got 10% slower for real visitors

  +10%

  Over the last 25 four-week periods to 2026-10-10, real Chrome visitors' tap response (inp) went from 84 ms to 97 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

• Not enough real-visitor data yet

  Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

• About 0.3 g of CO₂ per visit

  0.34 g

  By the Sustainable Web Design model, a visit to your homepage emits about 0.34 g of CO₂e: 40.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Not measured in this review.

• No meta description

  No meta description, so Google writes its own snippet from whatever text it finds.

• Title is short (21 characters)

  Your title is only 21 characters: “White Rabbit Projects”. Between 30 and 65 characters leaves room to say what you do and for whom.

  View source

• Only 0 internal links

  The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.

• No llms.txt

  There is no https://whiterabbitprojects.com/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.

• 2 small tap targets

  2 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

• 1 JavaScript error while loading

  1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

• Missing source maps

  Large scripts ship without source maps.

• No social proof

  No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

• Local business without LocalBusiness data

  Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  View source

• No phone number on the homepage

  A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

• No direct contact details

  No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

• Only about 42 words

  The homepage has only about 42 words of visible text; thin pages give Google and first-time buyers little to go on.

• No opening hours

  The homepage shows no opening hours. If customers visit or call, show when.

• No form on the homepage

  There is no form on the homepage, so every lead has to click through to another page first.

• No map or directions link

  There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

• No risk reducer

  No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

• 2 trackers load before any consent

  2

  Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (iubenda) is installed; check it blocks these until visitors agree where the law requires it.

• 8 other companies contacted

  Loading the homepage contacts 8 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.