vanillaicecakes.com website review

About 1.8 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.9 s faster on a phone.

About 81 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.

A phone's processor spends 5.8 s on main-thread work while loading, 2.9 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

8 third-party services load with your homepage (Google CDN, Shopify and Google Maps and others), adding 3.8 MB and 1.6 s of main-thread time.

10 images could be 449 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 750 ms faster on a phone.

Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.

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

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

Google CDN costs a phone 586 ms of main-thread work and 1.1 MB 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.

Shopify costs a phone 506 ms of main-thread work and 1.6 MB 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.

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

Google Maps costs a phone 191 ms of main-thread work and 468 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.

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

11 KiB JavaScript is shipped twice across bundles.

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

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

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

Your largest element takes 26.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three-tiered cake with pink roses.”.

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

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

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

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

Scripts block taps and scrolling for 216 ms in total while the page loads. Good is under 200 ms.

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.

Your homepage downloads 20.7 MB in 442 requests on a phone: media 14.0 MB (3), scripts 3.5 MB (226) and other files 1.5 MB (160). Under 2 MB keeps phones on slow connections fast.

5 images (307 KiB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

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

11 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

1 frame has no title, so screen-reader users cannot tell what it contains.

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

2 images have no alt text, which hurts accessibility and image search.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (3 elements).

Your title is 70 characters, so Google will cut it off around 60: “Vanilla Ice Cakes - Freshly Baked Cakes, Wedding And Celebration Cakes”.

Your meta description is 187 characters; Google truncates after about 160, so the end of your pitch is cut.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 28 pages on vanillaicecakes.com and 9 external pages.

The HTML your server sends has 194 of the 389 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.

There is no https://vanillaicecakes.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.

We fetched 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

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

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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.

Social proof on the homepage: 2 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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

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

The homepage carries about 389 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Microsoft Clarity and 1 more (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 17 cookies (measured from a US location before any click).

No known cookie consent tool loads with the page. Some sites build their own banner, and some only show one to visitors from the EU.

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