Website review, no card needed
honeyrevenge.com website review
Visit site (opens in a new tab)Reviewed 16 November 202634 issues · 77 checks
This review found 34 issues worth fixing on honeyrevenge.com, 9 of them high impact, across 77 checks. The most urgent: improve image delivery. 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- #68,781 of 123,845 reviewed websitesbeats 39%
- #44,529 of 69,695 online storesbeats 31%
- #42,344 of 63,398 Shopify storesbeats 28%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 976 ms |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.1 s |
| Jun 20, 2026 | 1.1 s |
| Jun 27, 2026 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.0 s |
| Jul 18, 2026 | 979 ms |
| Jul 25, 2026 | 943 ms |
| Aug 1, 2026 | 956 ms |
| Aug 8, 2026 | 943 ms |
| Aug 15, 2026 | 945 ms |
| Aug 22, 2026 | 945 ms |
| Aug 29, 2026 | 911 ms |
| Sep 5, 2026 | 886 ms |
| Sep 12, 2026 | 864 ms |
| Sep 19, 2026 | 848 ms |
| Sep 26, 2026 | 870 ms |
| Oct 3, 2026 | 861 ms |
| Oct 10, 2026 | 835 ms |
| Oct 17, 2026 | 861 ms |
| Oct 24, 2026 | 888 ms |
| Oct 31, 2026 | 896 ms |
| Nov 7, 2026 | 940 ms |
| Nov 14, 2026 | 925 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 100 ms |
| Jun 20, 2026 | 103 ms |
| Jun 27, 2026 | 103 ms |
| Jul 4, 2026 | 103 ms |
| Jul 11, 2026 | 99 ms |
| Jul 18, 2026 | 93 ms |
| Jul 25, 2026 | 89 ms |
| Aug 1, 2026 | 96 ms |
| Aug 8, 2026 | 99 ms |
| Aug 15, 2026 | 102 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 105 ms |
| Sep 5, 2026 | 103 ms |
| Sep 12, 2026 | 102 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 112 ms |
| Oct 3, 2026 | 121 ms |
| Oct 10, 2026 | 122 ms |
| Oct 17, 2026 | 123 ms |
| Oct 24, 2026 | 123 ms |
| Oct 31, 2026 | 116 ms |
| Nov 7, 2026 | 113 ms |
| Nov 14, 2026 | 104 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
0.8 s
1.5 s
2.3 s
3.1 s
3.8 s
4.6 s
5.4 s
6.1 s
Speed
Improve image delivery
3.0 s · 1.4 MB13 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 3.0 s faster on a phone.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.0 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 (spotifycdn.com, Facebook and bandsintown.com and others), adding 2.6 MB and 1.5 s of main-thread time.
Reduce unused JavaScript
300 ms · 1.1 MBAbout 1.1 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 300 ms faster on a phone.
Mobile performance score: 50
50/100Your mobile performance score is 50. Pages that score under 90 lose visitors before the first paint.
spotifycdn.com adds 813 ms
813 msspotifycdn.com costs a phone 813 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.
Use efficient cache lifetimes
350 ms · 587 KiB15 files are served with short cache lifetimes, so returning visitors download them again (587 KiB).
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 259 ms. During a long task the page ignores taps.
bandsintown.com adds 186 ms
186 msbandsintown.com costs a phone 186 ms of main-thread work and 448 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.
Spotify adds 25 ms
25 msSpotify costs a phone 25 ms of main-thread work and 332 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.
Render-blocking requests
150 ms6 files block the first paint until they finish downloading. Deferring or inlining them could save about 150 ms.
Duplicated JavaScript
38 KiB38 KiB JavaScript is shipped twice across bundles.
Legacy JavaScript
17 KiBPolyfills for old browsers add 17 KiB JavaScript that modern phones do not need.
Reduce unused CSS
12 KiBAbout 12 KiB of CSS is downloaded but never applied on this page.
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: 7 ms
7 msYour server sent the HTML in 7 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Time to Interactive: 24.6 s
24.6 sThe page becomes fully interactive after 24.6 s. Good is under 3.8 s.
Largest Contentful Paint: 8.4 s
8.4 sYour largest element takes 8.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Speed Index: 13.3 s
13.3 sVisually, the page fills in at 13.3 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 633 ms
633 msScripts block taps and scrolling for 633 ms in total while the page loads. Good is under 200 ms.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 95 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 checks passed
Passes Core Web Vitals for real visitors
Real Chrome users on phones pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)).
Real-user LCP: 1.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 121 ms
121 msReal visitors wait 121 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
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: 0.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 410 ms
410 msReal visitors wait 410 ms for your server to start answering (75th percentile). Good is under 800 ms.
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.001
0.001The layout barely moves while loading (CLS 0.001, good is under 0.1).
Images and page weight
Page weight: 7.3 MB in 229 requests
7.3 MBYour homepage downloads 7.3 MB in 229 requests on a phone: scripts 4.2 MB (81), images 1.8 MB (19) and other files 689 KiB (95). Under 2 MB keeps phones on slow connections fast.
About 2.1 g of CO₂ per visit
2.06 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.06 g of CO₂e: 247.6 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical by axe-core.
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.
6 tap targets too small
6 tap targets are too small or too close together to hit reliably with a finger.
button, link, and menuitem elements do not have accessible names.
button, link, and menuitem elements do not have accessible names. (1 element).
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 27 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (13 characters)
Your title is only 13 characters: “Honey Revenge”. 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.
47 internal links, 25 external
The homepage links to 47 pages on honeyrevenge.com and 25 external pages.
6 checks passed
Meta description: 97 characters
Your meta description is 97 characters: “Official website for the pop rock band, Honey Revenge. Shop apparel, music, accessories and more!”.
One H1 headline
Your main headline reads: “Tour Dates”.
Canonical URL set
The canonical URL is https://honeyrevenge.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://honeyrevenge.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://honeyrevenge.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
1 page without a meta description
https://honeyrevenge.com/collections/tees has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://honeyrevenge.com/products/hrevtmosbl-ts and https://honeyrevenge.com/products/hrevtsstbl-ts use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://honeyrevenge.com/collections/tees has 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 21 found) and read each the way a search engine does.
5 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.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 4 pages that loaded have a <title>.
Best practices
2 third-party cookies
2 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
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.
Thin social proof
Social proof on the homepage: 3 trust badges. 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 10 words
The homepage has only about 10 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.
3 checks passed
7 calls to action
The homepage has 7 calls to action, for example “SHOP”, “order” and “SHOP ALL”.
11 short forms
11 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Meta Pixel.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 honeyrevenge.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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Yuri Facebook Multi Pixels · railway.app
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
- The footer still says © 2025.
Stack
- CMS
- Webflow
- 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 34 issues on honeyrevenge.com, including 15 speed issues, 2 SEO issues and 4 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.