Website review, no card needed
q-dance.com website review
Visit site (opens in a new tab)Reviewed 6 November 202643 issues · 72 checks
This review found 43 issues worth fixing on q-dance.com, 14 of them high impact, across 72 checks. The most urgent: use efficient cache lifetimes. 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
69D- #101,131 of 117,615 reviewed websitesbeats 12%
- #61,456 of 66,923 online storesbeats 7%
- #56,812 of 61,018 Shopify storesbeats 6%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.6 s |
| May 30, 2026 | 2.4 s |
| Jun 6, 2026 | 2.3 s |
| Jun 13, 2026 | 2.2 s |
| Jun 20, 2026 | 2.2 s |
| Jun 27, 2026 | 2.0 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.9 s |
| Jul 25, 2026 | 1.9 s |
| Aug 1, 2026 | 2.3 s |
| Aug 8, 2026 | 2.6 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 3.0 s |
| Aug 29, 2026 | 3.1 s |
| Sep 5, 2026 | 3.1 s |
| Sep 12, 2026 | 3.0 s |
| Sep 19, 2026 | 3.0 s |
| Sep 26, 2026 | 3.0 s |
| Oct 3, 2026 | 2.7 s |
| Oct 10, 2026 | 2.7 s |
| Oct 17, 2026 | 2.7 s |
| Oct 24, 2026 | 2.7 s |
| Oct 31, 2026 | 2.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 149 ms |
| May 23, 2026 | 139 ms |
| May 30, 2026 | 138 ms |
| Jun 6, 2026 | 139 ms |
| Jun 13, 2026 | 137 ms |
| Jun 20, 2026 | 143 ms |
| Jun 27, 2026 | 130 ms |
| Jul 4, 2026 | 126 ms |
| Jul 11, 2026 | 127 ms |
| Jul 18, 2026 | 127 ms |
| Jul 25, 2026 | 133 ms |
| Aug 1, 2026 | 171 ms |
| Aug 8, 2026 | 184 ms |
| Aug 15, 2026 | 189 ms |
| Aug 22, 2026 | 195 ms |
| Aug 29, 2026 | 196 ms |
| Sep 5, 2026 | 195 ms |
| Sep 12, 2026 | 181 ms |
| Sep 19, 2026 | 181 ms |
| Sep 26, 2026 | 181 ms |
| Oct 3, 2026 | 182 ms |
| Oct 10, 2026 | 184 ms |
| Oct 17, 2026 | 187 ms |
| Oct 24, 2026 | 186 ms |
| Oct 31, 2026 | 183 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.9 s
1.9 s
2.8 s
3.7 s
4.7 s
5.6 s
6.6 s
7.5 s
Speed
Use efficient cache lifetimes
10.4 s · 1.8 MB10 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Reduce unused JavaScript
6.6 s · 1.3 MBAbout 1.3 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 6.6 s faster on a phone.
Render-blocking requests
7.8 s5 files block the first paint until they finish downloading. Deferring or inlining them could save about 7.8 s.
Mobile performance score: 39
39/100Your mobile performance score is 39. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Reduce unused CSS
780 ms · 190 KiBAbout 190 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 780 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (listenlive.co, Google Tag Manager and superstruct.services and others), adding 1.3 MB and 580 ms of main-thread time.
Font display
700 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 700 ms).
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 293 ms. During a long task the page ignores taps.
listenlive.co adds 167 ms
167 mslistenlive.co costs a phone 167 ms of main-thread work and 363 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.
superstruct.services adds 95 ms
95 mssuperstruct.services costs a phone 95 ms of main-thread work and 388 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.
Improve image delivery
200 ms · 50 KiB1 image could be 50 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 200 ms faster on a phone.
Legacy JavaScript
15 KiBPolyfills for old browsers add 15 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.
2 checks passed
Main-thread work: 2.0 s
A phone's processor spends 2.0 s on main-thread work while loading, 831 ms of it running JavaScript. That is comfortably low.
Server response: 1 ms
1 msYour server sent the HTML in 1 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.
First Contentful Paint: 10.5 s
10.5 sThe first text or image appears after 10.5 s on a phone. Good is under 1.8 s.
Largest Contentful Paint: 19.1 s
19.1 sYour largest element takes 19.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Early access to Defqon.1 ticketsales”.
Time to Interactive: 19.1 s
19.1 sThe page becomes fully interactive after 19.1 s. Good is under 3.8 s.
Speed Index: 10.5 s
10.5 sVisually, the page fills in at 10.5 s (Speed Index). Good is under 3.4 s.
Real-user LCP: 2.7 s
2.7 sReal visitors wait 2.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Tap response (INP) got 28% slower for real visitors
+28%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 149 ms to 183 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 464 ms
464 msScripts block taps and scrolling for 464 ms in total while the page loads. Good is under 200 ms.
Cumulative Layout Shift: 0.14
0.14The layout shifts by 0.14 while loading, so content jumps under the reader's thumb. Good is under 0.1.
Largest content (LCP) held steady for real visitors
-3%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
4 checks passed
Real-user INP: 200 ms
200 msReal visitors wait 200 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Real-user FCP: 1.8 s
1.8 sReal visitors see the first content after 1.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 277 ms
277 msReal visitors wait 277 ms for your server to start answering (75th percentile). Good is under 800 ms.
Images and page weight
Page weight: 2.8 MB in 33 requests
2.8 MBYour homepage downloads 2.8 MB in 33 requests on a phone: scripts 2.2 MB (12), other files 267 KiB (11) and stylesheets 266 KiB (3). Under 2 MB keeps phones on slow connections fast.
1 image far larger than shown
46 KiB1 image is downloaded at several times the size a phone draws it, for example 4860.jpg at 500 px wide, shown at 60 px. Resized copies would save about 46 KiB.
1 image in older formats
1 image (52 KiB) is 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 0.8 g of CO₂ per visit
0.81 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.81 g of CO₂e: 96.9 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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
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.
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.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 43 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 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
No meta description
No meta description, so Google writes its own snippet from whatever text it finds.
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
Title is short (7 characters)
Your title is only 7 characters: “Q-dance”. 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.
No canonical URL
No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
Only 0 internal links
The homepage links to only 0 pages on your own site, so visitors and crawlers find few routes into the rest of it.
2 links crawlers can't follow
2 links have no real href, so search engines can't follow them.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
2 checks passed
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.q-dance.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://www.q-dance.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.
Best practices
11 small tap targets
11 of 19 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
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 403 ()”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 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 93 words
The homepage has only about 93 words of visible text; thin pages give Google and first-time buyers little to go on.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
2 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP” and “REGISTER”.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
1 cookie set on arrival
1Opening the homepage sets 1 cookie, 1 of them by other companies (measured from a US location before any click).
12 other companies contacted
Loading the homepage contacts 12 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) 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 q-dance.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 Plus
- Hosting
- AWS
Company
- Headquarters
- Amsterdam
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 43 issues on q-dance.com, including 19 speed issues, 8 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.