Website review, no card needed

nutoncycling.com logo

nutoncycling.com website review

Visit site (opens in a new tab)Reviewed 11 November 202629 issues · 77 checks

This review found 29 issues worth fixing on nutoncycling.com, 5 of them high impact, across 77 checks. The most urgent: use efficient cache lifetimes. 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.3 s1.0 sMay 23Nov 71.0 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20261.3 s
May 30, 20261.2 s
Jun 6, 20261.1 s
Jun 13, 20261.1 s
Jun 20, 20261.1 s
Jun 27, 20261.1 s
Jul 4, 20261.1 s
Jul 11, 20261.2 s
Jul 18, 20261.2 s
Jul 25, 20261.2 s
Aug 1, 20261.3 s
Aug 8, 20261.2 s
Aug 15, 20261.3 s
Aug 22, 20261.2 s
Aug 29, 20261.3 s
Sep 5, 20261.3 s
Sep 12, 20261.3 s
Sep 19, 20261.3 s
Sep 26, 20261.2 s
Oct 3, 20261.2 s
Oct 10, 20261.2 s
Oct 17, 20261.2 s
Oct 24, 20261.1 s
Oct 31, 20261.1 s
Nov 7, 20261.0 s
Real-visitor tap response (INP)75th percentile, phones
92 ms66 msMay 23Nov 779 ms
Show as table
DateReal-visitor tap response (INP)
May 23, 202678 ms
May 30, 202675 ms
Jun 6, 202669 ms
Jun 13, 202672 ms
Jun 20, 202674 ms
Jun 27, 202675 ms
Jul 4, 202674 ms
Jul 11, 202675 ms
Jul 18, 202675 ms
Jul 25, 202675 ms
Aug 1, 202680 ms
Aug 8, 202684 ms
Aug 15, 202686 ms
Aug 22, 202688 ms
Aug 29, 202689 ms
Sep 5, 202682 ms
Sep 12, 202678 ms
Sep 19, 202677 ms
Sep 26, 202676 ms
Oct 3, 202678 ms
Oct 10, 202679 ms
Oct 17, 202682 ms
Oct 24, 202682 ms
Oct 31, 202681 ms
Nov 7, 202679 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 nutoncycling.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. nutoncycling.com at 0.6 s0.6 s
  2. nutoncycling.com at 1.3 s1.3 s
  3. nutoncycling.com at 1.9 s1.9 s
  4. nutoncycling.com at 2.5 s2.5 s
  5. nutoncycling.com at 3.2 s3.2 s
  6. nutoncycling.com at 3.8 s3.8 s
  7. nutoncycling.com at 4.4 s4.4 s
  8. nutoncycling.com at 5.1 s5.1 s

Speed

6 to fix74
  • Use efficient cache lifetimes

    1.1 s · 99 KiB

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

  • Mobile performance score: 74

    74/100

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

  • Render-blocking requests

    800 ms

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

  • Reduce unused JavaScript

    450 ms · 91 KiB

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

  • Main-thread work: 2.9 s

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

  • 2,785 HTML elements

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

  • 3 third-party services on the page

    3 third-party services load with your homepage (Shopify, shop.app and zegsuapps.com), adding 278 KiB and 200 ms of main-thread time.

  • Improve image delivery

    150 ms · 37 KiB

    2 images could be 37 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

  • Reduce unused CSS

    150 ms · 31 KiB

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

  • Legacy JavaScript

    150 ms · 7 KiB

    Polyfills for old browsers add 7 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.

  • 7 long tasks on the main thread

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

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

1 checks passed
  • Server response: 7 ms

    7 ms

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

Core Web Vitals

4 to fix100
  • Largest Contentful Paint: 5.4 s

    5.4 s

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

  • Time to Interactive: 6.1 s

    6.1 s

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

  • Speed Index: 3.7 s

    3.7 s

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

  • Total Blocking Time: 238 ms

    238 ms

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

  • Tap response (INP) held steady for real visitors

    +5%

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

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

    1.1 s

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

  • Real-user INP: 79 ms

    79 ms

    Real visitors wait 79 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: 0.7 s

    0.7 s

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

  • Real-user TTFB: 438 ms

    438 ms

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

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

    -12%

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

  • First Contentful Paint: 1.1 s

    1.1 s

    The first text or image appears after 1.1 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).

Images and page weight

100
  • About 0.5 g of CO₂ per visit

    0.52 g

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

    1.8 MB

    Your homepage downloads 1.8 MB in 184 requests on a phone: other files 758 KiB (103), images 471 KiB (18) and scripts 398 KiB (50). 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

4 to fixGoogle 9595
  • Hidden but focusable

    1 element hidden from screen readers can still receive keyboard focus.

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

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

  • 1 form field without a label

    1 form field has 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.

  • Headings skip levels

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

2 checks passed
  • Every image has alt text

    All 33 images in the HTML carry an alt attribute.

  • 48 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 3 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 10086
  • Title is short (13 characters)

    Your title is only 13 characters: “Nuton Cycling”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Nuton Cycling” and “NUTON センターロック用 ロックリング”). One clear main headline is easier for people and search engines.

  • No favicon declared

    No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

  • 44 internal links, 5 external

    The homepage links to 44 pages on nutoncycling.com and 5 external pages.

6 checks passed
  • Meta description: 117 characters

    Your meta description is 117 characters: “「NUTON / ニュートン」は日本発のスポーツバイク専用・軽量パーツブランドです。 We are a lightweight bicycle products brand from Japan. Designed in Japan.”.

  • Canonical URL set

    The canonical URL is https://nutoncycling.com/en.

  • Structured data in place

    Structured data found: Product.

  • 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://nutoncycling.com/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://nutoncycling.com/llms.txt (5 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

4 to fix78
  • 2 pages share a title

    https://nutoncycling.com/en/pages/%E3%81%8A%E5%95%8F%E3%81%84%E5%90%88%E3%82%8F%E3%81%9B and https://nutoncycling.com/en/pages/contact all use the title “お問い合わせ – Nuton Cycling”. Search engines can't tell which page to show for a search, so each competes with the others.

  • 6 pages without a meta description

    https://nutoncycling.com/en/collections/cassette-%E3%82%B9%E3%83%97%E3%83%AD%E3%82%B1%E3%83%83%E3%83%88, https://nutoncycling.com/en/collections/null1-cassette, https://nutoncycling.com/en/collections/accessories-%E3%82%A2%E3%82%AF%E3%82%BB%E3%82%B5%E3%83%AA%E3%83%BC, https://nutoncycling.com/en/pages/dealer, https://nutoncycling.com/en/pages/faq and https://nutoncycling.com/en/pages/contact have no meta description, so Google writes the search snippet from whatever text it finds.

  • 9 links to non-canonical URLs

    Your homepage links to 9 pages by a URL that isn't their canonical one, for example https://nutoncycling.com/en/collections/cassette-%E3%82%B9%E3%83%97%E3%83%AD%E3%82%B1%E3%83%83%E3%83%88, whose canonical is https://nutoncycling.com/en/collections/cassette-%e3%82%b9%e3%83%97%e3%83%ad%e3%82%b1%e3%83%83%e3%83%88. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

  • 4 pages without an H1

    https://nutoncycling.com/en/pages/dealer, https://nutoncycling.com/en/pages/faq, https://nutoncycling.com/en/pages/%E3%81%8A%E5%95%8F%E3%81%84%E5%90%88%E3%82%8F%E3%81%9B and https://nutoncycling.com/en/pages/contact have no <h1> headline, so visitors and search engines get no clear main topic.

  • 3 pages slow to respond

    https://nutoncycling.com/en/collections/null1-cassette, https://nutoncycling.com/en/products/nuton-null%CB%A2-hg-12s and https://nutoncycling.com/en/collections/accessories-%E3%82%A2%E3%82%AF%E3%82%BB%E3%82%B5%E3%83%AA%E3%83%BC took over 3 s to send their HTML from our server.

  • 13 internal pages checked

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

3 checks passed
  • Linked pages load

    All 13 pages we checked loaded without an error.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 13 pages that loaded have a <title>.

Best practices

2 to fixGoogle 9687
  • 4 small tap targets

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

  • 2 JavaScript errors while loading

    2 errors were logged to the browser console while the page loaded, for example “Error producing monorail event MonorailRequestError: Error completing request. A network failure may have prevented the…”.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix50
  • 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 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 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 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
  • 4 calls to action

    The homepage has 4 calls to action, for example “CONTACT” and “icon-email Subscribe”.

  • 6 short forms

    6 short forms (1 field at most) are right on the homepage.

Privacy and tracking

  • 6 cookies set on arrival

    6

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

  • 7 other companies contacted

    Loading the homepage contacts 7 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 nutoncycling.com, 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 nutoncycling.com, including 10 speed issues, 3 SEO issues and 5 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