Website review, no card needed
plushshop.com website review
Visit site (opens in a new tab)Reviewed 4 November 202646 issues · 90 checks
This review found 46 issues worth fixing on plushshop.com, 17 of them high impact, across 90 checks. The most urgent: main-thread work: 26.4 s. 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
65D- #109,174 of 117,615 reviewed websitesbeats 6%
- #64,565 of 66,923 online storesbeats 3%
- #59,250 of 61,018 Shopify storesbeats 2%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.6 s |
| May 23, 2026 | 1.5 s |
| May 30, 2026 | 1.5 s |
| Jun 6, 2026 | 1.5 s |
| Jun 13, 2026 | 1.4 s |
| Jun 20, 2026 | 1.4 s |
| Jun 27, 2026 | 1.4 s |
| Jul 4, 2026 | 1.5 s |
| Jul 11, 2026 | 1.5 s |
| Jul 18, 2026 | 1.5 s |
| Jul 25, 2026 | 1.5 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.5 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.5 s |
| Sep 26, 2026 | 1.5 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.5 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.5 s |
| Oct 31, 2026 | 1.5 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 178 ms |
| May 23, 2026 | 183 ms |
| May 30, 2026 | 184 ms |
| Jun 6, 2026 | 184 ms |
| Jun 13, 2026 | 183 ms |
| Jun 20, 2026 | 182 ms |
| Jun 27, 2026 | 184 ms |
| Jul 4, 2026 | 188 ms |
| Jul 11, 2026 | 193 ms |
| Jul 18, 2026 | 194 ms |
| Jul 25, 2026 | 195 ms |
| Aug 1, 2026 | 196 ms |
| Aug 8, 2026 | 197 ms |
| Aug 15, 2026 | 201 ms |
| Aug 22, 2026 | 201 ms |
| Aug 29, 2026 | 200 ms |
| Sep 5, 2026 | 197 ms |
| Sep 12, 2026 | 194 ms |
| Sep 19, 2026 | 194 ms |
| Sep 26, 2026 | 193 ms |
| Oct 3, 2026 | 191 ms |
| Oct 10, 2026 | 190 ms |
| Oct 17, 2026 | 189 ms |
| Oct 24, 2026 | 188 ms |
| Oct 31, 2026 | 191 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
2.4 s
4.8 s
7.3 s
9.7 s
12.1 s
14.5 s
16.9 s
19.3 s
Speed
Main-thread work: 26.4 s
A phone's processor spends 26.4 s on main-thread work while loading, 5.5 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Shopify adds 1.7 s
1.7 sShopify costs a phone 1.7 s of main-thread work and 1,006 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.
Mobile performance score: 18
18/100Your mobile performance score is 18. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8,497 HTML elements
The page has 8,497 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Snapchat and cloudfront.net and others), adding 1.3 MB and 2.8 s of main-thread time.
Reduce unused CSS
600 ms · 114 KiBAbout 114 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
Improve image delivery
500 ms · 172 KiB9 images could be 172 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 476 ms. During a long task the page ignores taps.
Reduce unused JavaScript
379 KiBAbout 379 KiB of JavaScript is downloaded but never used on this page.
Snapchat adds 345 ms
345 msSnapchat costs a phone 345 ms of main-thread work and 63 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.
cloudfront.net adds 326 ms
326 mscloudfront.net costs a phone 326 ms of main-thread work and 43 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
53 KiB15 files are served with short cache lifetimes, so returning visitors download them again (53 KiB).
Duplicated JavaScript
47 KiB47 KiB JavaScript is shipped twice across bundles.
Minify JavaScript
39 KiB39 KiB could be saved by minifying JavaScript.
Legacy JavaScript
21 KiBPolyfills for old browsers add 21 KiB JavaScript that modern phones do not need.
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.
1 checks passed
Server response: 14 ms
14 msYour server sent the HTML in 14 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.
Largest Contentful Paint: 10.5 s
10.5 sYour largest element takes 10.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Total Blocking Time: 5.8 s
5.8 sScripts block taps and scrolling for 5.8 s in total while the page loads. Good is under 200 ms.
Time to Interactive: 22.7 s
22.7 sThe page becomes fully interactive after 22.7 s. Good is under 3.8 s.
Speed Index: 9.5 s
9.5 sVisually, the page fills in at 9.5 s (Speed Index). Good is under 3.4 s.
Cumulative Layout Shift: 0.304
0.304The layout shifts by 0.304 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Real-user INP: 336 ms
336 msReal visitors wait 336 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
11 images without width and height
11 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 178 ms to 191 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-5%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user LCP: 2.3 s
2.3 sReal visitors wait 2.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
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: 594 ms
594 msReal visitors wait 594 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 5.4 MB in 405 requests
5.4 MBYour homepage downloads 5.4 MB in 405 requests on a phone: images 3.1 MB (178), scripts 1.0 MB (88) and other files 736 KiB (94). Under 2 MB keeps phones on slow connections fast.
11 images far larger than shown
885 KiB11 images are downloaded at several times the size a phone draws them, for example misacosplay.png at 1,009 px wide, shown at 199 px. Resized copies would save about 885 KiB.
33 images below the first screen load straight away
33 images further down the page (1.8 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
An image on the first screen is lazy-loaded
20260909190248_5168_257.jpg 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).
14 images in older formats
14 images (443 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.
About 1.5 g of CO₂ per visit
1.53 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.53 g of CO₂e: 183.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
62 text elements with low contrast
62 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 images without alt text
9 images have no alt text, which hurts accessibility and image search.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.
2 form fields without a label
2 form fields have no label, so screen readers announce an empty box and autofill guesses.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 checks passed
53 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 58 WCAG 2.2 A/AA and best-practice rules on the phone render: 53 passed and 5 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
One H1 headline
Your <h1> is empty.
188 internal links, 25 external
The homepage links to 188 pages on plushshop.com and 25 external pages.
7 checks passed
Meta description: 158 characters
Your meta description is 158 characters: “Shop anime plushies and Meow Meow Family character plush toys at PLUSHSHOP. Soft, huggable collectibles for fans and co…”.
Title: 62 characters
Your title is a healthy 62 characters: “PLUSHSHOP.COM|Anime Plushies & 17inch Meow Meow Cat Plush Toys”.
Canonical URL set
The canonical URL is https://www.plushshop.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://www.plushshop.com/sitemap.xml.
AI search readiness
No llms.txt
There is no https://www.plushshop.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.
3 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 (2,997 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without a title
https://www.plushshop.com/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.plushshop.com/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://www.plushshop.com/collections/all and https://www.plushshop.com/customer_authentication/redirect have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.plushshop.com/customer_authentication/redirect and https://www.plushshop.com/pages/shippinganddelivery have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 91 found) and read each the way a search engine does.
3 checks passed
Linked pages load
4 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.
Best practices
14 small tap targets
14 of 36 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Authorization will not be covered by the wildcard symbol (*) in CORS `Access-Control-Allow-Headers`…”).
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
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.
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.
Thin social proof
Social proof on the homepage: 195 testimonial or review blocks. 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.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
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.
About 1,547 words of copy
The homepage carries about 1,547 words of visible text.
Urgency cues
The page uses urgency cues (a countdown or limited-time wording).
2 checks passed
6 calls to action
The homepage has 6 calls to action, for example “BUY”, “START >” and “HOW PRE ORDER WORK”.
65 short forms
65 short forms (1 field at most) are right on the homepage.
Privacy and tracking
9 trackers load before any consent
9Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Meta Pixel and Pinterest Tag and 4 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.
23 cookies set on arrival
23Opening the homepage sets 23 cookies (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 plushshop.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
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 46 issues on plushshop.com, including 21 speed issues, 1 SEO issue and 6 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.