Website review, no card needed
hoppenly.com website review
Visit site (opens in a new tab)Reviewed 10 November 202632 issues · 79 checks
This review found 32 issues worth fixing on hoppenly.com, 8 of them high impact, across 79 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- #61,215 of 108,881 reviewed websitesbeats 39%
- #39,746 of 61,767 online storesbeats 31%
- #37,869 of 56,365 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.8 s |
| Jun 13, 2026 | 2.9 s |
| Jun 20, 2026 | 2.9 s |
| Jun 27, 2026 | 2.9 s |
| Jul 4, 2026 | 2.9 s |
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
Reduce unused JavaScript
1.2 s · 263 KiBAbout 263 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 66
66/100Your mobile performance score is 66. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
550 ms · 222 KiB12 images could be 222 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 550 ms faster on a phone.
Render-blocking requests
350 ms2 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
Main-thread work: 2.4 s
A phone's processor spends 2.4 s on main-thread work while loading, 768 ms of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
1,667 HTML elements
The page has 1,667 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
6 third-party services on the page
6 third-party services load with your homepage (Google Tag Manager, Shopify and Google/Doubleclick Ads and others), adding 229 KiB and 187 ms of main-thread time.
Reduce unused CSS
150 ms · 28 KiBAbout 28 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
4 long tasks on the main thread
4 long tasks block the main thread while loading, the longest for 146 ms. During a long task the page ignores taps.
Minify CSS
6 KiB6 KiB could be saved by minifying CSS.
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.
Minify JavaScript
3 KiB3 KiB could be saved by minifying JavaScript.
1 checks passed
Server response: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 7.1 s
7.1 sYour largest element takes 7.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 6.0 s
6.0 sVisually, the page fills in at 6.0 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 7.1 s
7.1 sThe page becomes fully interactive after 7.1 s. Good is under 3.8 s.
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.
Largest content (LCP) held steady for real visitors
+9%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 2.6 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
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: 137 ms
137 msScripts block the page for only 137 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.8 MB in 199 requests
12.8 MBYour homepage downloads 12.8 MB in 199 requests on a phone: media 10.9 MB (1), other files 736 KiB (81) and images 519 KiB (44). Under 2 MB keeps phones on slow connections fast.
About 3.6 g of CO₂ per visit
3.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.63 g of CO₂e: 435.7 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
Hidden but focusable
15 elements hidden from screen readers can still receive keyboard focus.
12 text elements with low contrast
12 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (7 elements)
All page content should be contained by landmarks: 7 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
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.
51 links without text
51 visible links have no text or label, so screen readers cannot say where they go.
4 form fields without a label
4 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.
1 checks passed
40 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 48 WCAG 2.2 A/AA and best-practice rules on the phone render: 40 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (23 characters)
Your title is only 23 characters: “Shop Hoppenly® Official”. 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.
94 internal links, 1 external
The homepage links to 94 pages on hoppenly.com and 1 external page.
6 checks passed
Meta description: 146 characters
Your meta description is 146 characters: “Home of the Cheer Duck and Custom Stuffed Animals. Whether you're a cheerleading athlete, fan, or collector, Hoppenly® …”.
One H1 headline
Your main headline reads: “Hoppenly”.
Canonical URL set
The canonical URL is https://hoppenly.com/.
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://hoppenly.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.
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 (217 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://hoppenly.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages share a meta description
https://hoppenly.com/collections/frontpage, https://hoppenly.com/collections/exclusive-banana, https://hoppenly.com/pages/contact, https://hoppenly.com/collections/voyage-collection, https://hoppenly.com/collections/hot-selling and https://hoppenly.com/collections/tie-dye use the same meta description. A description written for each page earns more clicks.
6 pages without an H1
https://hoppenly.com/collections/frontpage, https://hoppenly.com/collections/exclusive-banana, https://hoppenly.com/pages/contact, https://hoppenly.com/collections/voyage-collection, https://hoppenly.com/collections/hot-selling and https://hoppenly.com/collections/tie-dye have no <h1> headline, so visitors and search engines get no clear main topic.
2 pages with very little text
https://hoppenly.com/pages/contact and https://hoppenly.com/collections/voyage-collection 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.
3 pages slow to respond
https://hoppenly.com/collections/hot-selling, https://hoppenly.com/collections/tie-dye and https://hoppenly.com/products/hoppenly-exclusive-stingray took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 35 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
46 small tap targets
46 of 91 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Scrolls sideways on phones
On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.
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”.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
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 150 words
The homepage has only about 150 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: “Shop”.
13 calls to action
The homepage has 13 calls to action, for example “Contact Us”, “Quick Shop” and “Contact”.
2 short forms
2 short forms (1 field at most) are right on the homepage, asking for an email.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager and Meta 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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
13 other companies contacted
Loading the homepage contacts 13 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 hoppenly.com, 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 3 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Parkour Facebook Pixel · King Product Options · Judge Me Reviews
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
- Analytics
- Google Analytics
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on hoppenly.com, including 10 speed issues, 2 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.