Website review, no card needed
yt-industries.com website review
Visit site (opens in a new tab)Reviewed 30 October 202633 issues · 81 checks
This review found 33 issues worth fixing on yt-industries.com, 12 of them high impact, across 81 checks. The most urgent: page weight: 16.1 MB in 232 requests. 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
73CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 3.3 s |
| May 16, 2026 | 3.3 s |
| May 23, 2026 | 3.3 s |
| May 30, 2026 | 3.3 s |
| Jun 6, 2026 | 3.3 s |
| Jun 13, 2026 | 3.3 s |
| Jun 20, 2026 | 3.3 s |
| Jun 27, 2026 | 3.3 s |
| Jul 4, 2026 | 3.4 s |
| Jul 11, 2026 | 3.4 s |
| Jul 18, 2026 | 3.5 s |
| Jul 25, 2026 | 3.5 s |
| Aug 1, 2026 | 3.7 s |
| Aug 8, 2026 | 3.9 s |
| Aug 15, 2026 | 4.2 s |
| Aug 22, 2026 | 4.4 s |
| Aug 29, 2026 | 4.5 s |
| Sep 5, 2026 | 4.4 s |
| Sep 12, 2026 | 4.3 s |
| Sep 19, 2026 | 4.1 s |
| Sep 26, 2026 | 4.0 s |
| Oct 3, 2026 | 4.0 s |
| Oct 10, 2026 | 4.0 s |
| Oct 17, 2026 | 3.9 s |
| Oct 24, 2026 | 3.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 155 ms |
| May 16, 2026 | 155 ms |
| May 23, 2026 | 154 ms |
| May 30, 2026 | 152 ms |
| Jun 6, 2026 | 153 ms |
| Jun 13, 2026 | 156 ms |
| Jun 20, 2026 | 159 ms |
| Jun 27, 2026 | 164 ms |
| Jul 4, 2026 | 168 ms |
| Jul 11, 2026 | 168 ms |
| Jul 18, 2026 | 169 ms |
| Jul 25, 2026 | 169 ms |
| Aug 1, 2026 | 169 ms |
| Aug 8, 2026 | 171 ms |
| Aug 15, 2026 | 173 ms |
| Aug 22, 2026 | 175 ms |
| Aug 29, 2026 | 177 ms |
| Sep 5, 2026 | 178 ms |
| Sep 12, 2026 | 178 ms |
| Sep 19, 2026 | 179 ms |
| Sep 26, 2026 | 176 ms |
| Oct 3, 2026 | 176 ms |
| Oct 10, 2026 | 177 ms |
| Oct 17, 2026 | 174 ms |
| Oct 24, 2026 | 177 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.6 s
1.1 s
1.7 s
2.3 s
2.9 s
3.4 s
4.0 s
4.6 s
Speed
Render-blocking requests
1.1 s10 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.1 s.
Use efficient cache lifetimes
450 ms · 15.3 MB64 files are served with short cache lifetimes, so returning visitors download them again (15.3 MB).
Mobile performance score: 87
87/100Your mobile performance score is 87. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
286 KiB2 images could be 286 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
250 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 250 ms).
Reduce unused CSS
150 ms · 27 KiBAbout 27 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.
3 long tasks on the main thread
3 long tasks block the main thread while loading, the longest for 113 ms. During a long task the page ignores taps.
Reduce unused JavaScript
72 KiBAbout 72 KiB of JavaScript is downloaded but never used on this page.
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 third-party service on the page
1 third-party service load with your homepage (Google Tag Manager), adding 1 KiB and 0 ms of main-thread time.
2 checks passed
Main-thread work: 1.5 s
A phone's processor spends 1.5 s on main-thread work while loading, 622 ms of it running JavaScript. That is comfortably low.
Server response: 62 ms
62 msYour server sent the HTML in 62 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.
Real-user LCP: 4.1 s
4.1 sReal visitors wait 4.1 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 1.08
1.08For real visitors the layout shifts by 1.08 (75th percentile). Good is under 0.1.
Real-user FCP: 3.5 s
3.5 sReal visitors see the first content after 3.5 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.8 s
2.8 sReal visitors wait 2.8 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 7.1 s
7.1 sVisually, the page fills in at 7.1 s (Speed Index). Good is under 3.4 s.
Real-user INP: 206 ms
206 msReal visitors wait 206 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
First Contentful Paint: 2.4 s
2.4 sThe first text or image appears after 2.4 s on a phone. Good is under 1.8 s.
Time to Interactive: 5.0 s
5.0 sThe page becomes fully interactive after 5.0 s. Good is under 3.8 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) got 13% slower for real visitors
+13%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 155 ms to 177 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 3.3 s to 3.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Largest Contentful Paint: 2.4 s
2.4 sYour largest element renders in 2.4 s on a phone, inside Google's 2.5 s “good” threshold. The largest element is the text “Who says you're too old, too slow, too anything? We say it …”.
Total Blocking Time: 130 ms
130 msScripts block the page for only 130 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0.036
0.036The layout barely moves while loading (CLS 0.036, good is under 0.1).
Images and page weight
Page weight: 16.1 MB in 232 requests
16.1 MBYour homepage downloads 16.1 MB in 232 requests on a phone: media 8.6 MB (4), images 6.5 MB (47) and scripts 443 KiB (154). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
page_home_icon_mobile_400x400.png 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).
1 image in older formats
1 image (110 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 4.6 g of CO₂ per visit
4.55 gBy the Sustainable Web Design model, a visit to your homepage emits about 4.55 g of CO₂e: 546.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
2 text elements with low contrast
2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
Malformed lists
Some lists contain elements other than list items, which screen readers announce wrongly.
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.
35 links without text
35 visible links have no text or label, so screen readers cannot say where they go.
Alternative text of images should not be repeated as text (1 element)
Alternative text of images should not be repeated as text: 1 element on the page fails this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
2 checks passed
Every image has alt text
All 76 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 51 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 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 H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No favicon declared
No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.
106 internal links, 7 external
The homepage links to 106 pages on yt-industries.com and 7 external pages.
6 checks passed
Meta description: 154 characters
Your meta description is 154 characters: “Young Talent is what YT stands for. Our direct sales approach maximizes your budget, bringing your dream Enduro, Trail,…”.
Title: 45 characters
Your title is a healthy 45 characters: “YT Industries | Mountain Bikes | Live Uncaged”.
Canonical URL set
The canonical URL is https://www.yt-industries.com/.
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.yt-industries.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.yt-industries.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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (656 words), so crawlers that don't run JavaScript still read it.
Other pages
15 pages share a meta description
https://www.yt-industries.com/E-MTB/Avinox-Decoy-X/Uncover-the-Decoy-X, https://www.yt-industries.com/Bikes/All-Mountain-Jeffsy, https://www.yt-industries.com/Bikes/Enduro-Capra, https://www.yt-industries.com/Bikes/Trail-Izzo, https://www.yt-industries.com/Bikes/Downhill-Tues and https://www.yt-industries.com/Bikes/Gravel-Szepter and 9 others use the same meta description. A description written for each page earns more clicks.
1 page with very little text
https://www.yt-industries.com/Bikes/Junior-Primus 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.
2 pages slow to respond
https://www.yt-industries.com/Bikes/Dirt-Dirtlove and https://www.yt-industries.com/E-MTB/Bosch-Decoy took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 38 found) and read each the way a search engine does.
7 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.
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 15 pages that loaded have a <title>.
Best practices
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
2 checks passed
Tap targets are thumb-sized
29 of 32 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
Thin social proof
Social proof on the homepage: 2 trust badges. 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 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 213 words
The homepage has only about 213 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
2 calls to action
The homepage has 2 calls to action, for example “Subscribe” and “Contact”.
1 short form
A short form (2 fields at most) is right on the homepage, asking for an email.
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). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.
2 cookies set on arrival
2Opening the homepage sets 2 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.
1 other company contacted
Loading the homepage contacts 1 host 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 yt-industries.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Hosting
- AWS
Company
- Founded
- 2006
- Headquarters
- Forchheim
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 33 issues on yt-industries.com, including 14 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.