Website review, no card needed

novarock.shop logo

novarock.shop website review

Visit site (opens in a new tab)Reviewed 6 November 202629 issues · 79 checks

This review found 29 issues worth fixing on novarock.shop, 7 of them high impact, across 79 checks. The most urgent: certain ARIA roles must contain particular children (1 element). Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Real-visitor load time (LCP)75th percentile, phones
1.4 s786 msMay 16Oct 311.0 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20261.2 s
May 23, 20261.2 s
May 30, 20261.1 s
Jun 6, 2026855 ms
Jun 13, 2026866 ms
Jun 20, 2026874 ms
Jun 27, 2026866 ms
Jul 4, 2026927 ms
Jul 11, 2026993 ms
Jul 18, 20261.1 s
Jul 25, 20261.2 s
Aug 1, 20261.2 s
Aug 8, 20261.2 s
Aug 15, 20261.2 s
Aug 22, 20261.3 s
Aug 29, 20261.2 s
Sep 5, 20261.2 s
Sep 12, 20261.3 s
Sep 19, 20261.2 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.1 s
Oct 17, 20261.1 s
Oct 24, 20261.1 s
Oct 31, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
81 ms48 msMay 16Oct 3169 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 202652 ms
May 23, 202652 ms
May 30, 202652 ms
Jun 6, 202656 ms
Jun 13, 202661 ms
Jun 20, 202662 ms
Jun 27, 202662 ms
Jul 4, 202663 ms
Jul 11, 202664 ms
Jul 18, 202664 ms
Jul 25, 202665 ms
Aug 1, 202664 ms
Aug 8, 202665 ms
Aug 15, 202662 ms
Aug 22, 202667 ms
Aug 29, 202674 ms
Sep 5, 202673 ms
Sep 12, 202677 ms
Sep 19, 202670 ms
Sep 26, 202669 ms
Oct 3, 202671 ms
Oct 10, 202671 ms
Oct 17, 202671 ms
Oct 24, 202669 ms
Oct 31, 202669 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

Full-page screenshot of novarock.shop (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. novarock.shop at 0.5 s0.5 s
  2. novarock.shop at 1.1 s1.1 s
  3. novarock.shop at 1.6 s1.6 s
  4. novarock.shop at 2.1 s2.1 s
  5. novarock.shop at 2.7 s2.7 s
  6. novarock.shop at 3.2 s3.2 s
  7. novarock.shop at 3.7 s3.7 s
  8. novarock.shop at 4.3 s4.3 s

Speed

6 to fix72
  • Improve image delivery

    550 ms · 460 KiB

    23 images could be 460 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.

  • Mobile performance score: 72

    72/100

    Your mobile performance score is 72. Pages that score under 90 lose visitors before the first paint.

  • Reduce unused JavaScript

    340 ms · 113 KiB

    About 113 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 340 ms faster on a phone.

  • Use efficient cache lifetimes

    300 ms · 148 KiB

    6 files are served with short cache lifetimes, so returning visitors download them again (148 KiB).

  • Render-blocking requests

    350 ms

    5 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.

  • consentmanager.net adds 267 ms

    267 ms

    consentmanager.net costs a phone 267 ms of main-thread work and 157 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.

  • 4 third-party services on the page

    4 third-party services load with your homepage (consentmanager.net, Shopify and shop.app and others), adding 264 KiB and 286 ms of main-thread time.

  • Reduce unused CSS

    140 ms · 36 KiB

    About 36 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 140 ms faster on a phone.

  • 2 long tasks on the main thread

    2 long tasks block the main thread while loading, the longest for 72 ms. During a long task the page ignores taps.

  • Font display

    50 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).

  • 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.5 s

    A phone's processor spends 1.5 s on main-thread work while loading, 611 ms of it running JavaScript. That is comfortably low.

  • Server response: 5 ms

    5 ms

    Your server sent the HTML in 5 ms, well inside Google's 600 ms guideline.

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 7.8 s

    7.8 s

    Your largest element takes 7.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Nova Rock Festival Grim Reaper T-Shirt 446418”.

  • Time to Interactive: 8.3 s

    8.3 s

    The page becomes fully interactive after 8.3 s. Good is under 3.8 s.

  • Tap response (INP) got 33% slower for real visitors

    +33%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 52 ms to 69 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Speed Index: 5.0 s

    5.0 s

    Visually, the page fills in at 5.0 s (Speed Index). Good is under 3.4 s.

10 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.3 s

    1.3 s

    Real visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.

  • Real-user INP: 74 ms

    74 ms

    Real visitors wait 74 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

  • Real-user CLS: 0.00

    0.00

    For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.

  • Real-user FCP: 1.0 s

    1.0 s

    Real visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.

  • Real-user TTFB: 459 ms

    459 ms

    Real visitors wait 459 ms for your server to start answering (75th percentile). Good is under 800 ms.

  • Largest content (LCP) got 10% faster for real visitors

    -10%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.2 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

  • Cumulative Layout Shift: 0

    0

    The layout barely moves while loading (CLS 0, good is under 0.1).

  • First Contentful Paint: 0.9 s

    0.9 s

    The first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.

  • Total Blocking Time: 11 ms

    11 ms

    Scripts block the page for only 11 ms while loading. Good is under 200 ms.

Images and page weight

2 to fix83
  • Page weight: 2.7 MB in 167 requests

    2.7 MB

    Your homepage downloads 2.7 MB in 167 requests on a phone: images 1.4 MB (32), other files 735 KiB (81) and scripts 460 KiB (43). Under 2 MB keeps phones on slow connections fast.

  • An image on the first screen is lazy-loaded

    novarock_backgr_d6ce7ffd-9087-4056-8511-d40b74051fd2.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).

  • 2 images below the first screen load straight away

    2 images further down the page (45 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 0.8 g of CO₂ per visit

    0.77 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.77 g of CO₂e: 91.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

2 checks passed
  • Images use modern formats

    Every sizeable image is WebP, AVIF or SVG.

  • Images are sized for phones

    No image is downloaded at more than three times the size it is drawn on a phone.

Accessibility

4 to fixGoogle 9294
  • Certain ARIA roles must contain particular children (1 element)

    Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

  • 6 tap targets too small

    6 tap targets are too small or too close together to hit reliably with a finger.

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate 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.

  • Headings skip levels

    Headings skip levels (h1 → h4), which makes the page harder to scan with a screen reader.

2 checks passed
  • Every image has alt text

    All 27 images in the HTML carry an alt attribute.

  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 4 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

3 to fixGoogle 10086
  • No structured data

    No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

  • Meta description is short (18 characters)

    Your meta description is only 18 characters: “Nova Rock Festival”. 70 to 160 characters is enough to sell the click.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Nova Rock Festival” and “Nova Rock Festival”). One clear main headline is easier for people and search engines.

  • 72 internal links, 2 external

    The homepage links to 72 pages on novarock.shop and 2 external pages.

5 checks passed
  • Title: 39 characters

    Your title is a healthy 39 characters: “Nova Rock Festival - Nova Rock Festival”.

  • Canonical URL set

    The canonical URL is https://www.novarock.shop/.

  • 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.novarock.shop/sitemap.xml.

AI search readiness

1 to fix83
  • 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.

2 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.

  • llms.txt published

    The site publishes https://www.novarock.shop/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

2 to fix90
  • 4 pages share 2 titles

    https://www.novarock.shop/products/nova-rock-festival-winds-of-rock-117940 and https://www.novarock.shop/products/nova-rock-festival-kidss-winds-of-rock-117942 all use the title “Winds of Rock - Nova Rock Festival”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

  • 13 pages share a meta description

    https://www.novarock.shop/collections/t-shirts, https://www.novarock.shop/collections/sweats-hoods, https://www.novarock.shop/collections/accessories, https://www.novarock.shop/collections/sale, https://www.novarock.shop/products/nova-rock-festival-grim-reaper-117963 and https://www.novarock.shop/products/nova-rock-festival-beast-of-nova-117964 and 7 others use the same meta description. A description written for each page earns more clicks.

  • 4 pages with very little text

    https://www.novarock.shop/collections/t-shirts, https://www.novarock.shop/collections/sweats-hoods, https://www.novarock.shop/collections/accessories and https://www.novarock.shop/collections/sale 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.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 28 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.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

1 to fixGoogle 9293
  • 23 small tap targets

    23 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 1 low-resolution image

    1 image is served at too low a resolution for sharp phone screens.

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

6 to fix36
  • 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 calls to action

    We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

  • 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 67 words

    The homepage has only about 67 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.

1 checks passed
  • 1 short form

    A short form (0 fields at most) is right on the homepage.

Privacy and tracking

  • 2 trackers load before any consent

    2

    Before a visitor clicks anything, the page loads Google Ads and Google Tag Manager (measured from a US location before any click). A consent tool (consentmanager) is installed; check it blocks these until visitors agree where the law requires it.

  • 8 cookies set on arrival

    8

    Opening the homepage sets 8 cookies (measured from a US location before any click).

  • 9 other companies contacted

    Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: consentmanager

    A consent management tool (consentmanager) loads with the page.

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 novarock.shop, 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 29 issues on novarock.shop, including 10 speed issues, 3 SEO issues 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25