Website review, no card needed
jellylandusa.com website review
Visit site (opens in a new tab)Reviewed 12 November 202642 issues · 77 checks
This review found 42 issues worth fixing on jellylandusa.com, 16 of them high impact, across 77 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
One score from every part of this review. How it works
How it loaded on a phone
1.1 s
2.2 s
3.3 s
4.4 s
5.5 s
6.6 s
7.7 s
8.7 s
Speed
Reduce unused JavaScript
12.0 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 12.0 s faster on a phone.
Use efficient cache lifetimes
1.9 s · 640 KiB35 files are served with short cache lifetimes, so returning visitors download them again (640 KiB).
Render-blocking requests
1.6 s31 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Improve image delivery
1.1 s · 406 KiB5 images could be 406 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 1.1 s faster on a phone.
Main-thread work: 5.2 s
A phone's processor spends 5.2 s on main-thread work while loading, 2.5 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, Google CDN and Google Tag Manager and others), adding 41.1 MB and 2.0 s of main-thread time.
Shopify adds 737 ms
737 msShopify costs a phone 737 ms of main-thread work and 38.3 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.
Mobile performance score: 52
52/100Your mobile performance score is 52. Pages that score under 90 lose visitors before the first paint.
Google CDN adds 462 ms
462 msGoogle CDN costs a phone 462 ms of main-thread work and 1.4 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.
Google Tag Manager adds 352 ms
352 msGoogle Tag Manager costs a phone 352 ms of main-thread work and 671 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.
activitymessenger.com adds 172 ms
172 msactivitymessenger.com costs a phone 172 ms of main-thread work and 422 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
180 ms · 99 KiBAbout 99 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 180 ms faster on a phone.
11 long tasks on the main thread
11 long tasks block the main thread while loading, the longest for 135 ms. During a long task the page ignores taps.
Minify JavaScript
57 KiB57 KiB could be saved by minifying JavaScript.
Minify CSS
34 KiB34 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.
1 checks passed
Server response: 3 ms
3 msYour server sent the HTML in 3 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 12.5 s
12.5 sThe first text or image appears after 12.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 35.5 s
35.5 sYour largest element takes 35.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “A Cute Kid & Kidult Shoppe Play, Create & Celebrate! We're …”.
Time to Interactive: 35.6 s
35.6 sThe page becomes fully interactive after 35.6 s. Good is under 3.8 s.
Speed Index: 15.4 s
15.4 sVisually, the page fills in at 15.4 s (Speed Index). Good is under 3.4 s.
12 images without width and height
12 images have no width and height attributes, so the layout jumps as each one loads.
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.
2 checks passed
Total Blocking Time: 198 ms
198 msScripts block the page for only 198 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: 64.1 MB in 215 requests
64.1 MBYour homepage downloads 64.1 MB in 215 requests on a phone: media 57.7 MB (8), scripts 2.8 MB (64) and images 2.0 MB (56). Under 2 MB keeps phones on slow connections fast.
2 images over 500 KB
2 images weigh 1.2 MB together. On a phone connection a single image that size takes seconds.
2 images far larger than shown
61 KiB2 images are downloaded at several times the size a phone draws them, for example centerbottom-BNXnEpqd.png at 1,103 px wide, shown at 275 px. Resized copies would save about 61 KiB.
3 images below the first screen load straight away
3 images further down the page (164 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
1 image in older formats
1 image (40 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.
About 18.2 g of CO₂ per visit
18.17 gBy the Sustainable Web Design model, a visit to your homepage emits about 18.17 g of CO₂e: 2180.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
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.
3 form fields without a label
3 form fields have no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h1 → h3), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 67 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 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 2 failed. 5 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
Title is short (16 characters)
Your title is only 16 characters: “Jellyland | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
3 H1 headlines
There are 3 <h1> headlines (“Play, Create & Celebrate!”, “Design, Decorate & DIY!” and “Smile, Collect & Discover!”). One clear main headline is easier for people and search engines.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
39 internal links, 4 external
The homepage links to 39 pages on jellylandusa.com and 4 external pages.
2 checks passed
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://jellylandusa.com/sitemap.xml.
AI search readiness
No Organization structured data
There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.
No llms.txt
There is no https://jellylandusa.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.
1 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.
Other pages
2 pages without a title
https://jellylandusa.com/pages/contact and https://jellylandusa.com/pages/investment-opportunities have no <title>, so Google invents the link text in results.
7 pages share a title
https://jellylandusa.com/collections/all-products, https://jellylandusa.com/collections/slimes, https://jellylandusa.com/collections/accessory, https://jellylandusa.com/collections/keychains, https://jellylandusa.com/collections/stationery and https://jellylandusa.com/collections/kawaii-merchandise and 1 other all use the title “Jellyland | Products”. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages without a meta description
https://jellylandusa.com/collections/all-products, https://jellylandusa.com/collections/slimes, https://jellylandusa.com/collections/accessory, https://jellylandusa.com/collections/keychains, https://jellylandusa.com/collections/stationery and https://jellylandusa.com/collections/kawaii-merchandise and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.
8 pages without an H1
https://jellylandusa.com/collections/all-products, https://jellylandusa.com/collections/slimes, https://jellylandusa.com/collections/accessory, https://jellylandusa.com/collections/keychains, https://jellylandusa.com/collections/stationery and https://jellylandusa.com/collections/kawaii-merchandise and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://jellylandusa.com/pages/book-your-event and https://jellylandusa.com/pages/store-policies have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 13 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Best practices
3 small tap targets
3 of 10 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
3 third-party cookies
3 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
3 low-resolution images
3 images are served at too low a resolution for sharp phone screens.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
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.
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 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 143 words
The homepage has only about 143 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.
2 checks passed
13 calls to action
The homepage has 13 calls to action, for example “Shop”, “Book Event” and “Contact Us”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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.
7 cookies set on arrival
7Opening the homepage sets 7 cookies, 4 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.
22 other companies contacted
Loading the homepage contacts 22 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 jellylandusa.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
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 42 issues on jellylandusa.com, including 16 speed issues, 6 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.