Website review, no card needed
freeze-frame.uk website review
Visit site (opens in a new tab)Reviewed 7 November 202647 issues · 93 checks
This review found 47 issues worth fixing on freeze-frame.uk, 14 of them high impact, across 93 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
77C- #69,607 of 125,621 reviewed websitesbeats 39%
- #44,806 of 70,216 online storesbeats 31%
- #42,585 of 63,788 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.4 s |
| May 23, 2026 | 1.4 s |
| May 30, 2026 | 1.4 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 27, 2026 | 1.6 s |
| Jul 25, 2026 | 1.4 s |
| Aug 15, 2026 | 1.6 s |
| Aug 29, 2026 | 1.9 s |
| Sep 5, 2026 | 1.9 s |
| Sep 19, 2026 | 1.9 s |
| Oct 10, 2026 | 1.8 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 162 ms |
| May 23, 2026 | 158 ms |
| May 30, 2026 | 181 ms |
| Jun 6, 2026 | 187 ms |
| Jun 13, 2026 | 195 ms |
| Jun 27, 2026 | 189 ms |
| Aug 15, 2026 | 208 ms |
| Aug 29, 2026 | 259 ms |
| Sep 5, 2026 | 257 ms |
| Sep 19, 2026 | 241 ms |
| Oct 10, 2026 | 238 ms |
| Oct 17, 2026 | 230 ms |
| Oct 24, 2026 | 194 ms |
| Oct 31, 2026 | 200 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
1.6 s
3.1 s
4.7 s
6.2 s
7.8 s
9.3 s
10.9 s
12.4 s
Speed
Reduce unused JavaScript
1.5 s · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.
Shopify adds 1.5 s
1.5 sShopify costs a phone 1.5 s of main-thread work and 789 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Render-blocking requests
1.5 s7 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Main-thread work: 7.3 s
A phone's processor spends 7.3 s on main-thread work while loading, 3.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, chatra.io and Yotpo and others), adding 1.9 MB and 2.4 s of main-thread time.
Improve image delivery
750 ms · 274 KiB13 images could be 274 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.
Mobile performance score: 55
55/100Your mobile performance score is 55. Pages that score under 90 lose visitors before the first paint.
chatra.io adds 475 ms
475 mschatra.io costs a phone 475 ms of main-thread work and 396 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.
Use efficient cache lifetimes
50 ms · 346 KiB18 files are served with short cache lifetimes, so returning visitors download them again (346 KiB).
Reduce unused CSS
300 ms · 88 KiBAbout 88 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
1,934 HTML elements
The page has 1,934 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 167 ms. During a long task the page ignores taps.
Legacy JavaScript
47 KiBPolyfills for old browsers add 47 KiB JavaScript that modern phones do not need.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Minify CSS
4 KiB4 KiB could be saved by minifying CSS.
1 checks passed
Server response: 10 ms
10 msYour server sent the HTML in 10 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 25.2 s
25.2 sThe page becomes fully interactive after 25.2 s. Good is under 3.8 s.
Largest Contentful Paint: 9.2 s
9.2 sYour largest element takes 9.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “LIFT SAGGING EYELIDS”.
Speed Index: 15.4 s
15.4 sVisually, the page fills in at 15.4 s (Speed Index). Good is under 3.4 s.
Tap response (INP) got 23% slower for real visitors
+23%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 162 ms to 200 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
First Contentful Paint: 2.6 s
2.6 sThe first text or image appears after 2.6 s on a phone. Good is under 1.8 s.
Total Blocking Time: 297 ms
297 msScripts block taps and scrolling for 297 ms in total while the page loads. Good is under 200 ms.
Largest content (LCP) got 11% slower for real visitors
+11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.6 s
1.6 sReal visitors wait 1.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 188 ms
188 msReal visitors wait 188 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.5 s
1.5 sReal visitors see the first content after 1.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 452 ms
452 msReal visitors wait 452 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.022
0.022The layout barely moves while loading (CLS 0.022, good is under 0.1).
Images and page weight
Page weight: 4.9 MB in 465 requests
4.9 MBYour homepage downloads 4.9 MB in 465 requests on a phone: scripts 2.2 MB (99), other files 1.2 MB (293) and images 1,016 KiB (52). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
30_OFF_PORE_PERFECTION_BUNDLE_mobile.png is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).
3 images far larger than shown
117 KiB3 images are downloaded at several times the size a phone draws them, for example 240702_FREEZEFRAME_REBRAND9854.png at 1,364 px wide, shown at 317 px. Resized copies would save about 117 KiB.
1 image in older formats
1 image (37 KiB) is 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.
1 image below the first screen load straight away
1 image further down the page (39 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.4 g of CO₂ per visit
1.38 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.38 g of CO₂e: 165.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Scrollable region must have keyboard access (9 elements)
Scrollable region must have keyboard access: 9 elements on the page fail this check, rated serious by axe-core.
6 text elements with low contrast
6 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
43 images without alt text
43 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
25 links without text
25 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h3 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 57 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 10 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (28 characters)
Your title is only 28 characters: “freezeframe – freezeframe-uk”. Between 30 and 65 characters leaves room to say what you do and for whom.
Meta description is long (174 characters)
Your meta description is 174 characters; Google truncates after about 160, so the end of your pitch is cut.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
126 internal links, 13 external
The homepage links to 126 pages on freeze-frame.uk and 13 external pages.
5 checks passed
Canonical URL set
The canonical URL is https://www.freeze-frame.uk/.
Structured data in place
Structured data found: Organization and WebSite.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.freeze-frame.uk/sitemap.xml.
AI search readiness
4 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Organization data: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (595 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.freeze-frame.uk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
8 pages share a meta description
https://www.freeze-frame.uk/collections/new-arrivals, https://www.freeze-frame.uk/collections/best-sellers, https://www.freeze-frame.uk/collections/award-winners, https://www.freeze-frame.uk/collections/gifts, https://www.freeze-frame.uk/collections/lip-solutions and https://www.freeze-frame.uk/collections/minimize-fine-lines-wrinkles and 2 others use the same meta description. A description written for each page earns more clicks.
14 pages without an H1
https://www.freeze-frame.uk/collections/new-arrivals, https://www.freeze-frame.uk/collections/best-sellers, https://www.freeze-frame.uk/collections/award-winners, https://www.freeze-frame.uk/collections/gifts, https://www.freeze-frame.uk/collections/all-products and https://www.freeze-frame.uk/collections/injection-solutions and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.
1 page slow to respond
https://www.freeze-frame.uk/collections/erase-eyebags-crows-feet took over 3 s to send its HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 46 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
9 small tap targets
9 of 45 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 3 deprecated browser APIs that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).
5 JavaScript errors while loading
5 errors were logged to the browser console while the page loaded, for example “Access to fetch at 'https://wishlist.webcontrive.com/wishlist-club/public/api/v2/setting' from origin 'https://www.free…”.
15 distorted images
15 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.
Thin social proof
Social proof on the homepage: 8 customer or partner logos. Pairing it with named testimonials or customer logos makes it far more convincing.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
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 159 words
The homepage has only about 159 words of visible text; thin pages give Google and first-time buyers little to go on.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
3 checks passed
22 calls to action
The homepage has 22 calls to action, for example “Shop All”, “Shop all” and “Shop All Show menu”.
17 short forms
17 short forms (1 field at most) are right on the homepage.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel 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.
17 cookies set on arrival
17Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).
No consent tool detected
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.
48 other companies contacted
Loading the homepage contacts 48 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at freeze-frame.uk, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
Your storefront loads 16 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Eg Auto Add To Cart · Yotpo Product Reviews · Tolstoy · Triplewhale · Klaviyo Email Marketing Sms · Cartbite · Forms · Thank You Page · Wishlist Club · herokuapp.com · rechargecdn.com · chatra.io · nfcube.com · cloudfront.net · bogos.io · useamp.com
Apps found in the homepage's code. Apps that only run in checkout or the admin aren't seen, and a headless storefront shows none. App data from programmable.info
Upkeep, stack and company
Stack
- Framework
- Tailwind CSS
- E-commerce
- Shopify
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 47 issues on freeze-frame.uk, including 17 speed issues, 5 SEO issues and 5 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.