Website review, no card needed
goldieblox.com website review
Visit site (opens in a new tab)Reviewed 5 November 202631 issues · 82 checks
This review found 31 issues worth fixing on goldieblox.com, 12 of them high impact, across 82 checks. The most urgent: render-blocking requests. 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
74C- #86,601 of 123,940 reviewed websitesbeats 26%
- #54,458 of 69,726 online storesbeats 18%
- #51,167 of 63,429 Shopify storesbeats 16%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.7 s |
| May 30, 2026 | 1.7 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.5 s |
| Jun 20, 2026 | 1.5 s |
| Jun 27, 2026 | 1.5 s |
| Jul 4, 2026 | 1.7 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.4 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.4 s |
| Sep 12, 2026 | 1.4 s |
| Sep 19, 2026 | 1.3 s |
| Sep 26, 2026 | 1.2 s |
| Oct 3, 2026 | 1.2 s |
| Oct 10, 2026 | 1.2 s |
| Oct 17, 2026 | 1.3 s |
| Oct 24, 2026 | 1.4 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 83 ms |
| May 23, 2026 | 78 ms |
| May 30, 2026 | 79 ms |
| Jun 6, 2026 | 80 ms |
| Jun 13, 2026 | 80 ms |
| Jun 20, 2026 | 82 ms |
| Jun 27, 2026 | 82 ms |
| Jul 4, 2026 | 88 ms |
| Jul 11, 2026 | 79 ms |
| Jul 18, 2026 | 75 ms |
| Jul 25, 2026 | 74 ms |
| Aug 1, 2026 | 71 ms |
| Aug 8, 2026 | 75 ms |
| Aug 15, 2026 | 86 ms |
| Aug 22, 2026 | 86 ms |
| Aug 29, 2026 | 83 ms |
| Sep 5, 2026 | 79 ms |
| Sep 12, 2026 | 70 ms |
| Sep 19, 2026 | 70 ms |
| Sep 26, 2026 | 71 ms |
| Oct 3, 2026 | 72 ms |
| Oct 10, 2026 | 78 ms |
| Oct 17, 2026 | 78 ms |
| Oct 24, 2026 | 78 ms |
| Oct 31, 2026 | 81 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
Speed
Render-blocking requests
7.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.3 s.
Reduce unused JavaScript
3.7 s · 841 KiBAbout 841 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 3.7 s faster on a phone.
Use efficient cache lifetimes
3.6 s · 921 KiB40 files are served with short cache lifetimes, so returning visitors download them again (921 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Privy, Google Tag Manager and Bold Commerce and others), adding 1.9 MB and 1.1 s of main-thread time.
Mobile performance score: 53
53/100Your mobile performance score is 53. Pages that score under 90 lose visitors before the first paint.
Privy adds 419 ms
419 msPrivy costs a phone 419 ms of main-thread work and 884 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.
Reduce unused CSS
300 ms · 129 KiBAbout 129 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.
Main-thread work: 3.1 s
A phone's processor spends 3.1 s on main-thread work while loading, 1.4 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Tag Manager adds 241 ms
241 msGoogle Tag Manager costs a phone 241 ms of main-thread work and 315 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.
Legacy JavaScript
150 ms · 102 KiBPolyfills for old browsers add 102 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
172 KiB9 images could be 172 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 149 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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 JavaScript
2 KiB2 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 4 ms
4 msYour server sent the HTML in 4 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
First Contentful Paint: 15.3 s
15.3 sThe first text or image appears after 15.3 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 15.3 s
15.3 sYour largest element takes 15.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Our Award-Winning Construction Toys are Coming Back!”.
Time to Interactive: 25.9 s
25.9 sThe page becomes fully interactive after 25.9 s. Good is under 3.8 s.
Speed Index: 15.3 s
15.3 sVisually, the page fills in at 15.3 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.5 s
2.5 sReal visitors wait 2.5 s for the largest content to appear (75th percentile). Good is under 2.5 s.
5 images without width and height
5 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 83 ms to 81 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
6 checks passed
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 424 ms
424 msReal visitors wait 424 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) got 17% faster for real visitors
-17%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 167 ms
167 msScripts block the page for only 167 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 12.2 MB in 252 requests
12.2 MBYour homepage downloads 12.2 MB in 252 requests on a phone: media 8.3 MB (3), scripts 2.1 MB (94) and other files 746 KiB (97). Under 2 MB keeps phones on slow connections fast.
About 3.5 g of CO₂ per visit
3.45 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.45 g of CO₂e: 414.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
8 links without text
8 visible links have no text or label, so screen readers cannot say where they go.
Headings skip levels
Headings skip levels (h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 5 images in the HTML carry an alt attribute.
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 4 failed. 6 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (25 characters)
Your title is only 25 characters: “Official GoldieBlox Store”. Between 30 and 65 characters leaves room to say what you do and for whom.
4 H1 headlines
There are 4 <h1> headlines (“<img class="no-js-image" src="//goldieblox.com/cd…”, “Our Award-Winning Construction Toys are Coming Ba…” and “Celebrating 15 Years of Inspiring Tomorrow's Buil…”). One clear main headline is easier for people and search engines.
3 links with vague text
3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
50 internal links, 10 external
The homepage links to 50 pages on goldieblox.com and 10 external pages.
6 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “GoldieBlox creates awesome toys, games and entertainment for girls, designed to develop early interest in engineering a…”.
Canonical URL set
The canonical URL is https://goldieblox.com/.
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://goldieblox.com/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 (354 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://goldieblox.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 pages without a meta description
https://goldieblox.com/pages/shows and https://goldieblox.com/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 21 found) and read each the way a search engine does.
6 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
1 broken image
1 image failed to load on a phone, for example https://lantern.roeye.com/track.php?fingerprint=ec71703f-dc7c-4ed1-98bc-f6fb158d5869&referrer=&landingpage=https%3A%2F%2Fgoldieblox.com%2F&useragent=Mozilla%2F5.0%20(iPhone%3B%20CPU%20iPhone%20OS%2017.
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”.
2 checks passed
Tap targets are thumb-sized
17 of 21 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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 186 words
The homepage has only about 186 words of visible text; thin pages give Google and first-time buyers little to go on.
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.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “JOIN WAITLIST”.
4 calls to action
The homepage has 4 calls to action, for example “JOIN WAITLIST”, “Learn More” and “Contact Us”.
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
7 trackers load before any consent
7Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 2 mores (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.
18 cookies set on arrival
18Opening the homepage sets 18 cookies, 2 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.
44 other companies contacted
Loading the homepage contacts 44 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 goldieblox.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Apps on your store
No apps were seen in the code your storefront loads.
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
- E-commerce
- Shopify
- Hosting
- Shopify
Company
- Founded
- 2012
- Headquarters
- Los Angeles
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on goldieblox.com, including 16 speed issues, 4 SEO issues and 3 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.