Website review, no card needed
getsnug.co website review
Visit site (opens in a new tab)Reviewed 13 November 202625 issues · 65 checks
This review found 25 issues worth fixing on getsnug.co, 7 of them high impact, across 65 checks. The most urgent: page weight: 8.4 MB in 109 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
80B- #43,129 of 108,838 reviewed websitesbeats 55%
- #28,688 of 61,763 online storesbeats 47%
- #27,616 of 56,363 Shopify storesbeats 44%
Closest competitors among Shopify stores
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
0.6 s
1.2 s
1.9 s
2.5 s
3.1 s
3.7 s
4.3 s
4.9 s
Speed
Improve image delivery
700 ms · 353 KiB10 images could be 353 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.
Mobile performance score: 78
78/100Your mobile performance score is 78. Pages that score under 90 lose visitors before the first paint.
1,502 HTML elements
The page has 1,502 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
1 long task on the main thread
1 long task block the main thread while loading, the longest for 72 ms. During a long task the page ignores taps.
Render-blocking requests
50 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 50 ms.
3 third-party services on the page
3 third-party services load with your homepage (Shopify, shop.app and Google Fonts), adding 120 KiB and 31 ms of main-thread time.
Use efficient cache lifetimes
5 KiB3 files are served with short cache lifetimes, so returning visitors download them again (5 KiB).
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.
2 checks passed
Main-thread work: 1.2 s
A phone's processor spends 1.2 s on main-thread work while loading, 267 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 5.1 s
5.1 sYour largest element takes 5.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “The Bird Box”.
Time to Interactive: 5.1 s
5.1 sThe page becomes fully interactive after 5.1 s. Good is under 3.8 s.
First Contentful Paint: 1.9 s
1.9 sThe first text or image appears after 1.9 s on a phone. Good is under 1.8 s.
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.
3 checks passed
Speed Index: 3.2 s
3.2 sVisually, the page fills in at 3.2 s (Speed Index), inside the 3.4 s “good” threshold.
Cumulative Layout Shift: 0.065
0.065The layout barely moves while loading (CLS 0.065, good is under 0.1).
Total Blocking Time: 0 ms
0 msScripts block the page for only 0 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 8.4 MB in 109 requests
8.4 MBYour homepage downloads 8.4 MB in 109 requests on a phone: media 6.8 MB (1), images 727 KiB (18) and other files 612 KiB (51). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
68 KiB1 image is downloaded at several times the size a phone draws it, for example mm-logo.png at 1,200 px wide, shown at 160 px. Resized copies would save about 68 KiB.
6 images in older formats
6 images (240 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 2.4 g of CO₂ per visit
2.39 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.39 g of CO₂e: 286.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Accessibility
Scrollable region must have keyboard access (1 element)
Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.
7 images without alt text
7 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 53 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 3 failed. 2 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 (14 characters)
Your title is only 14 characters: “Merry Mischief”. Between 30 and 65 characters leaves room to say what you do and for whom.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
15 internal links, 0 external
The homepage links to 15 pages on getsnug.co and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “The Bird Box”.
Canonical URL set
The canonical URL is https://www.merrymischief.shop/.
Structured data in place
Structured data found: ProductGroup.
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.merrymischief.shop/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (1,125 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.merrymischief.shop/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page without a title
https://www.merrymischief.shop/customer_authentication/redirect has no <title>, so Google invents the link text in results.
1 linked page hidden from search
https://www.merrymischief.shop/customer_authentication/redirect is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
3 pages without a meta description
https://www.merrymischief.shop/pages/faq, https://www.merrymischief.shop/customer_authentication/redirect and https://www.merrymischief.shop/collections/all have no meta description, so Google writes the search snippet from whatever text it finds.
1 page without an H1
https://www.merrymischief.shop/customer_authentication/redirect has no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.merrymischief.shop/collections/all has 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.
3 internal pages checked
We fetched 3 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
All 3 pages we checked loaded without an error.
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
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”.
2 checks passed
Tap targets are thumb-sized
9 of 9 tappable elements near the top are at least 24 px.
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 analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 10-field form
Your longest form asks for 10 fields (3 required). Every extra field lowers completion.
About 345 words of copy
The homepage carries about 345 words of visible text.
4 checks passed
1 call to action
The homepage has 1 call to action, for example “Subscribe”.
Social proof on the page
Social proof on the homepage: 39 testimonial or review blocks and a star rating.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
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
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Meta Pixel, Microsoft Clarity and TikTok Pixel (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.
8 cookies set on arrival
8Opening the homepage sets 8 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.
10 other companies contacted
Loading the homepage contacts 10 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 getsnug.co, 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 25 issues on getsnug.co, including 6 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.