Website review, no card needed

punkride.com logo

punkride.com website review

Visit site (opens in a new tab)Reviewed 4 November 202613 issues · 74 checks

This review found 13 issues worth fixing on punkride.com, 2 of them high impact, across 74 checks. The most urgent: fails Core Web Vitals for real visitors. 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
3.7 s1.7 sMay 16Oct 311.9 s
Show as table
DateReal-visitor load time (LCP)
May 16, 20263.5 s
May 23, 20263.4 s
May 30, 20263.4 s
Jun 6, 20263.2 s
Jun 13, 20263.1 s
Jun 20, 20263.1 s
Jun 27, 20263.1 s
Jul 4, 20263.2 s
Jul 11, 20263.2 s
Jul 18, 20263.2 s
Jul 25, 20263.1 s
Aug 1, 20263.1 s
Aug 8, 20263.1 s
Aug 15, 20263.1 s
Aug 22, 20263.1 s
Aug 29, 20263.2 s
Sep 5, 20263.2 s
Sep 12, 20263.2 s
Sep 19, 20263.2 s
Sep 26, 20263.2 s
Oct 3, 20263.1 s
Oct 10, 20263.0 s
Oct 17, 20262.7 s
Oct 24, 20262.3 s
Oct 31, 20261.9 s
Real-visitor tap response (INP)75th percentile, phones
209 ms132 msMay 16Oct 31157 ms
Show as table
DateReal-visitor tap response (INP)
May 16, 2026141 ms
May 23, 2026159 ms
May 30, 2026185 ms
Jun 6, 2026200 ms
Jun 13, 2026198 ms
Jun 20, 2026185 ms
Jun 27, 2026175 ms
Jul 4, 2026167 ms
Jul 11, 2026163 ms
Jul 18, 2026169 ms
Jul 25, 2026172 ms
Aug 1, 2026182 ms
Aug 8, 2026187 ms
Aug 15, 2026189 ms
Aug 22, 2026191 ms
Aug 29, 2026188 ms
Sep 5, 2026195 ms
Sep 12, 2026200 ms
Sep 19, 2026197 ms
Sep 26, 2026195 ms
Oct 3, 2026194 ms
Oct 10, 2026188 ms
Oct 17, 2026182 ms
Oct 24, 2026170 ms
Oct 31, 2026157 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 punkride.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

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

Speed

2 to fix95
  • Render-blocking requests

    400 ms

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

  • 1,950 HTML elements

    The page has 1,950 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • Reduce unused JavaScript

    120 ms · 48 KiB

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

  • 1 long task on the main thread

    1 long task block the main thread while loading, the longest for 60 ms. During a long task the page ignores taps.

  • Reduce unused CSS

    40 KiB

    About 40 KiB of CSS is downloaded but never applied on this page.

  • Improve image delivery

    29 KiB

    2 images could be 29 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • 2 third-party services on the page

    2 third-party services load with your homepage (Shopify and shop.app), adding 75 KiB and 17 ms of main-thread time.

  • Use efficient cache lifetimes

    5 KiB

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

3 checks passed
  • Mobile performance score: 95

    95/100

    Your mobile performance score is 95. That is in Google's “good” band (90 and up).

  • Main-thread work: 1.1 s

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

  • Server response: 14 ms

    14 ms

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

Core Web Vitals

3 to fix100
  • 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 TTFB: 832 ms

    832 ms

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

  • Largest Contentful Paint: 2.9 s

    2.9 s

    Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “A man wearing a black helmet and a white t-shirt with a bla…”. Most of its time is resource load delay (1.2 s).

  • Tap response (INP) held steady for real visitors

    +9%

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

10 checks passed
  • Real-user LCP: 1.8 s

    1.8 s

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

  • Real-user INP: 156 ms

    156 ms

    Real visitors wait 156 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.4 s

    1.4 s

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

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

    -40%

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

  • Speed Index: 3.1 s

    3.1 s

    Visually, the page fills in at 3.1 s (Speed Index), inside the 3.4 s “good” threshold.

  • Time to Interactive: 2.9 s

    2.9 s

    The page is fully interactive after 2.9 s.

  • First Contentful Paint: 1.3 s

    1.3 s

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

  • Cumulative Layout Shift: 0

    0

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

  • Total Blocking Time: 10 ms

    10 ms

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

Images and page weight

100
  • About 0.4 g of CO₂ per visit

    0.36 g

    By the Sustainable Web Design model, a visit to your homepage emits about 0.36 g of CO₂e: 42.9 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.3 MB in 134 requests

    1.3 MB

    Your homepage downloads 1.3 MB in 134 requests on a phone: other files 748 KiB (84), scripts 257 KiB (38) and images 158 KiB (5). 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

1 to fixGoogle 10099
  • 26 links without text

    26 visible links have no text or label, so screen readers cannot say where they go.

2 checks passed
  • Every image has alt text

    All 31 images in the HTML carry an alt attribute.

  • 52 automated accessibility rules passed

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

SEO

2 to fixGoogle 10088
  • Title is long (68 characters)

    Your title is 68 characters, so Google will cut it off around 60: “Punk Ride | Electric Scooters, E-Bikes & Kids Scooters – Shop Online”.

  • Meta description is long (233 characters)

    Your meta description is 233 characters; Google truncates after about 160, so the end of your pitch is cut.

  • 310 internal links, 7 external

    The homepage links to 310 pages on punkride.com and 7 external pages.

6 checks passed
  • One H1 headline

    Your main headline reads: “Punk Ride”.

  • Canonical URL set

    The canonical URL is https://www.punkride.com/en-uk.

  • Structured data in place

    Structured data found: OnlineStore, WebPage and WebSite.

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

AI search readiness

100
  • No llms.txt

    There is no https://www.punkride.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.

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.

  • Organization data: 5 of 6 facts

    Your Organization JSON-LD gives name, url, logo, sameAs (social profiles) and contact details; description would complete it.

  • Text is in the HTML

    Your server sends the page's text in the HTML (1,200 words), so crawlers that don't run JavaScript still read it.

Other pages

100
  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 122 found) and read each the way a search engine does.

7 checks passed
  • Linked pages load

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

  • Every page has a meta description

    All 9 pages that loaded have a meta description.

  • Titles are unique

    Every page we checked has its own title.

  • 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 9 pages that loaded have a <title>.

Best practices

Google 96100
3 checks passed
  • No console errors

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

  • Tap targets are thumb-sized

    38 of 46 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

4 to fix64
  • 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.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • Thin social proof

    Social proof on the homepage: 8 testimonial or review blocks. Pairing it with named testimonials or customer logos makes it far more convincing.

  • No analytics detected

    No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

  • No opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • Phone number is not tap-to-call

    Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

  • About 383 words of copy

    The homepage carries about 383 words of visible text.

3 checks passed
  • 7 calls to action

    The homepage has 7 calls to action, for example “Contact & Help ↗”, “Contact & Help” and “Contact & Help↗”.

  • 5 short forms

    5 short forms (1 field at most) are right on the homepage, asking for an email.

  • Phone number on the homepage

    Your phone number is on the homepage.

Privacy and tracking

1 to fix
  • 4 trackers load before any consent

    4

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

  • 13 cookies set on arrival

    13

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

  • 15 other companies contacted

    Loading the homepage contacts 15 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 punkride.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 4 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Multifeeds · Sitemap Noindex Pro Seo · T Lab Ai Translate · Content Translation

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

Framework
Tailwind CSS
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 13 issues on punkride.com, including 5 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

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