Website review, no card needed

easykaraoke.co.uk logo

easykaraoke.co.uk website review

Visit site (opens in a new tab)Reviewed 10 November 202641 issues · 80 checks

This review found 41 issues worth fixing on easykaraoke.co.uk, 17 of them high impact, across 80 checks. The most urgent: render-blocking requests. 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
6.5 s6.0 sMay 23Nov 76.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20266.4 s
May 30, 20266.4 s
Jun 6, 20266.4 s
Jun 13, 20266.4 s
Jun 20, 20266.4 s
Jun 27, 20266.4 s
Jul 4, 20266.4 s
Jul 11, 20266.4 s
Jul 18, 20266.4 s
Jul 25, 20266.3 s
Aug 1, 20266.3 s
Aug 8, 20266.2 s
Aug 15, 20266.2 s
Aug 22, 20266.2 s
Aug 29, 20266.2 s
Sep 5, 20266.2 s
Sep 12, 20266.2 s
Sep 19, 20266.2 s
Sep 26, 20266.2 s
Oct 3, 20266.2 s
Oct 10, 20266.2 s
Oct 17, 20266.1 s
Oct 24, 20266.1 s
Oct 31, 20266.1 s
Nov 7, 20266.0 s
Real-visitor tap response (INP)75th percentile, phones
798 ms694 msMay 23Nov 7720 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 2026706 ms
May 30, 2026706 ms
Jun 6, 2026714 ms
Jun 13, 2026721 ms
Jun 20, 2026728 ms
Jun 27, 2026750 ms
Jul 4, 2026765 ms
Jul 11, 2026777 ms
Jul 18, 2026786 ms
Jul 25, 2026781 ms
Aug 1, 2026772 ms
Aug 8, 2026761 ms
Aug 15, 2026744 ms
Aug 22, 2026735 ms
Aug 29, 2026732 ms
Sep 5, 2026730 ms
Sep 12, 2026733 ms
Sep 19, 2026736 ms
Sep 26, 2026734 ms
Oct 3, 2026737 ms
Oct 10, 2026736 ms
Oct 17, 2026729 ms
Oct 24, 2026728 ms
Oct 31, 2026723 ms
Nov 7, 2026720 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 easykaraoke.co.uk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. easykaraoke.co.uk at 0.4 s0.4 s
  2. easykaraoke.co.uk at 0.8 s0.8 s
  3. easykaraoke.co.uk at 1.1 s1.1 s
  4. easykaraoke.co.uk at 1.5 s1.5 s
  5. easykaraoke.co.uk at 1.9 s1.9 s
  6. easykaraoke.co.uk at 2.3 s2.3 s
  7. easykaraoke.co.uk at 2.6 s2.6 s
  8. easykaraoke.co.uk at 3.0 s3.0 s

Speed

6 to fix35
  • Render-blocking requests

    3.5 s

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

  • Reduce unused JavaScript

    1.5 s · 624 KiB

    About 624 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

  • Mobile performance score: 35

    35/100

    Your mobile performance score is 35. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

  • Avoid multiple page redirects

    751 ms

    The page goes through 1 redirect before it starts loading, costing about 751 ms. Link and advertise the final URL directly.

  • 4 long tasks on the main thread

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

  • Main-thread work: 2.1 s

    A phone's processor spends 2.1 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

  • Reduce unused CSS

    270 ms · 82 KiB

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

  • Use efficient cache lifetimes

    150 ms · 49 KiB

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

  • Document request latency

    50 ms

    The HTML itself could arrive about 50 ms sooner: redirects, a slow server response or missing compression delay everything after it.

  • 5 third-party services on the page

    5 third-party services load with your homepage (Other Google APIs/SDKs, Google/Doubleclick Ads and Google Fonts and others), adding 112 KiB and 10 ms of main-thread time.

  • Legacy JavaScript

    10 KiB

    Polyfills for old browsers add 10 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.

1 checks passed
  • Server response: 201 ms

    201 ms

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

Core Web Vitals

12 to fix0
  • 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.

  • Real-user CLS: 0.34

    0.34

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

  • Largest Contentful Paint: 9.5 s

    9.5 s

    Your largest element takes 9.5 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.

  • First Contentful Paint: 6.5 s

    6.5 s

    The first text or image appears after 6.5 s on a phone. Good is under 1.8 s.

  • Time to Interactive: 10.6 s

    10.6 s

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

  • Cumulative Layout Shift: 0.337

    0.337

    The layout shifts by 0.337 while loading, so content jumps under the reader's thumb. Good is under 0.1.

  • Speed Index: 6.5 s

    6.5 s

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

  • Real-user LCP: 3.8 s

    3.8 s

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

  • Real-user INP: 301 ms

    301 ms

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

  • Real-user FCP: 2.6 s

    2.6 s

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

  • Real-user TTFB: 956 ms

    956 ms

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

  • Total Blocking Time: 330 ms

    330 ms

    Scripts block taps and scrolling for 330 ms in total while the page loads. Good is under 200 ms.

  • Tap response (INP) held steady for real visitors

    +2%

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

  • Largest content (LCP) held steady for real visitors

    -5%

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

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.45 g

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

4 checks passed
  • Page weight: 1.6 MB in 72 requests

    1.6 MB

    Your homepage downloads 1.6 MB in 72 requests on a phone: scripts 1.1 MB (12), HTML 274 KiB (2) and stylesheets 78 KiB (3). That is a lean page.

  • 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

8 to fixGoogle 8489
  • 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.

  • Hidden but focusable

    10 elements hidden from screen readers can still receive keyboard focus.

  • All page content should be contained by landmarks (24 elements)

    All page content should be contained by landmarks: 24 elements on the page fail this check, rated moderate by axe-core.

  • Heading levels should only increase by one (1 element)

    Heading levels should only increase by one: 1 element on the page fails this check, rated moderate by axe-core.

  • No main landmark

    The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 2 form fields without a label

    2 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 39 automated accessibility rules passed

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

SEO

3 to fixGoogle 9281
  • No H1 headline

    There is no <h1>, so neither visitors nor Google get a clear main headline.

  • Title is short (21 characters)

    Your title is only 21 characters: “EasyKaraoke - YouTube”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 1 link with vague text

    1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

  • 13 internal links, 2 external

    The homepage links to 13 pages on easykaraoke.co.uk and 2 external pages.

6 checks passed
  • Meta description: 142 characters

    Your meta description is 142 characters: “Please use the below in channel search bar to find other great karaoke hits!Professional renditions composed by Easy Ka…”.

  • Canonical URL set

    The canonical URL is https://www.youtube.com/channel/UC-tDkOgdiO7FPav2sF5nkUg.

  • Structured data in place

    Structured data found: ProfilePage.

  • 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.youtube.com/sitemaps/sitemap.xml.

AI search readiness

2 to fix63
  • Most text only appears after JavaScript runs

    17%

    A phone browser shows 150 words, but the HTML your server sends has only 26. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

  • 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.youtube.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

4 to fix70
  • 1 page without a title

    https://www.youtube.com/ads has no <title>, so Google invents the link text in results.

  • 4 pages without a meta description

    https://www.youtube.com/t/contact_us, https://www.youtube.com/ads, https://www.youtube.com/t/terms and https://www.youtube.com/t/privacy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 3 links to non-canonical URLs

    Your homepage links to 3 pages by a URL that isn't their canonical one, for example https://www.youtube.com/about/copyright, whose canonical is https://www.youtube.com/howyoutubeworks/copyright. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 3 pages without an H1

    /, https://www.youtube.com/ads and https://www.youtube.com/new have no <h1> headline, so visitors and search engines get no clear main topic.

  • 1 page with very little text

    https://www.youtube.com/about 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.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

3 checks passed
  • Linked pages load

    All 12 pages we checked loaded without an error.

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

Best practices

1 to fixGoogle 9674
  • No mobile viewport

    No viewport meta tag, so phones render the desktop layout zoomed out.

  • Missing source maps

    Large scripts ship without source maps.

2 checks passed
  • No console errors

    No JavaScript errors were logged while the page loaded on a phone.

  • Tap targets are thumb-sized

    41 of 43 tappable elements near the top are at least 24 px.

Content and conversion

4 to fix58
  • 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 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 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: “Subscribe”.

  • 1 call to action

    The homepage has 1 call to action, for example “Contact us”.

Privacy and tracking

1 to fix
  • 1 tracker load before any consent

    1

    Before a visitor clicks anything, the page loads Google Ads (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.

  • 7 cookies set on arrival

    7

    Opening the homepage sets 7 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.

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

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 easykaraoke.co.uk, 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
10 Shopify Products;Shopify;Shopify Plus
Hosting
IONOS

Upkeep, stack, hiring and company data from programmable.info

Go beyond the website

What your $25 Growth Playbook adds

This review found 41 issues on easykaraoke.co.uk, including 18 speed issues, 3 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

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