Website review, no card needed
hankookracetire.com website review
Visit site (opens in a new tab)Reviewed 8 November 202641 issues · 84 checks
This review found 41 issues worth fixing on hankookracetire.com, 14 of them high impact, across 84 checks. The most urgent: reduce unused JavaScript. 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
72C- #96,081 of 124,112 reviewed websitesbeats 19%
- #59,232 of 69,777 online storesbeats 12%
- #55,172 of 63,466 Shopify storesbeats 11%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 1.8 s |
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.8 s |
| Jun 13, 2026 | 1.8 s |
| Jun 20, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Oct 24, 2026 | 1.8 s |
| Oct 31, 2026 | 1.8 s |
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.4 s
0.8 s
1.1 s
1.5 s
1.9 s
2.3 s
2.6 s
3.0 s
Speed
Reduce unused JavaScript
4.6 s · 835 KiBAbout 835 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 4.6 s faster on a phone.
Use efficient cache lifetimes
1.1 s · 177 KiB14 files are served with short cache lifetimes, so returning visitors download them again (177 KiB).
Mobile performance score: 70
70/100Your mobile performance score is 70. Pages that score under 90 lose visitors before the first paint.
Render-blocking requests
950 ms4 files block the first paint until they finish downloading. Deferring or inlining them could save about 950 ms.
Reduce unused CSS
740 ms · 161 KiBAbout 161 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 740 ms faster on a phone.
8 third-party services on the page
8 third-party services load with your homepage (YouTube, Google Maps and Shopify and others), adding 2.0 MB and 600 ms of main-thread time.
Legacy JavaScript
450 ms · 108 KiBPolyfills for old browsers add 108 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 450 ms faster on a phone.
YouTube adds 324 ms
324 msYouTube costs a phone 324 ms of main-thread work and 1,000 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.
Main-thread work: 2.5 s
A phone's processor spends 2.5 s on main-thread work while loading, 1.1 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Google Maps adds 130 ms
130 msGoogle Maps costs a phone 130 ms of main-thread work and 460 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.
Shopify adds 102 ms
102 msShopify costs a phone 102 ms of main-thread work and 316 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 KiB9 images could be 200 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 108 ms. During a long task the page ignores taps.
Minify JavaScript
6 KiB6 KiB could be saved by minifying JavaScript.
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: 5 ms
5 msYour server sent the HTML in 5 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 CLS: 0.42
0.42For real visitors the layout shifts by 0.42 (75th percentile). Good is under 0.1.
Largest Contentful Paint: 20.1 s
20.1 sYour largest element takes 20.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Time to Interactive: 20.3 s
20.3 sThe page becomes fully interactive after 20.3 s. Good is under 3.8 s.
Speed Index: 5.1 s
5.1 sVisually, the page fills in at 5.1 s (Speed Index). Good is under 3.4 s.
7 images without width and height
7 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
0%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.8 s
1.8 sReal visitors wait 1.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 1.0 s
1.0 sReal visitors see the first content after 1.0 s (75th percentile). Good is under 1.8 s.
Cumulative Layout Shift: 0.081
0.081The layout barely moves while loading (CLS 0.081, good is under 0.1).
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Total Blocking Time: 47 ms
47 msScripts block the page for only 47 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 4.2 MB in 213 requests
4.2 MBYour homepage downloads 4.2 MB in 213 requests on a phone: scripts 1.8 MB (58), images 1.3 MB (34) and other files 755 KiB (101). Under 2 MB keeps phones on slow connections fast.
About 1.2 g of CO₂ per visit
1.19 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.19 g of CO₂e: 143.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
3 checks passed
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
Hidden but focusable
9 elements hidden from screen readers can still receive keyboard focus.
4 text elements with low contrast
4 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
[role="img"] and [role="image"] elements must have alternative text (1 element)
[role="img"] and [role="image"] elements must have alternative text: 1 element on the page fails this check, rated serious by axe-core.
2 images without alt text
2 images have no alt text, which hurts accessibility and image search.
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 (h3 → h5), which makes the page harder to scan with a screen reader.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (1 element).
1 checks passed
50 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 50 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is short (28 characters)
Your title is only 28 characters: “Hankook Race Tires of Europe”. Between 30 and 65 characters leaves room to say what you do and for whom.
2 H1 headlines
There are 2 <h1> headlines (“Welcome to Hankook Race Tire” and “Hankook Tire and Technology”). One clear main headline is easier for people and search engines.
Meta description is long (298 characters)
Your meta description is 298 characters; Google truncates after about 160, so the end of your pitch is cut.
Structured data has 2 problems
Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: sameAs is not an absolute URL ("facebook.com/hankookmotorsports")”.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
58 internal links, 2 external
The homepage links to 58 pages on hankookracetire.com and 2 external pages.
3 checks passed
Canonical URL set
The canonical URL is https://hankookracetire.com/.
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://hankookracetire.com/sitemap.xml.
AI search readiness
4 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: 4 of 6 facts
Your Organization JSON-LD gives name, url, logo and sameAs (social profiles); description and contact details would complete it.
Text is in the HTML
Your server sends the page's text in the HTML (574 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://hankookracetire.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
2 linked pages are broken
Your homepage links to https://hankookracetire.com/instagram.com/hankookmotorsports and https://hankookracetire.com/facebook.com/hankookmotorsports, which answer with an error. Visitors hit a dead end and search engines drop them.
1 page without a meta description
https://hankookracetire.com/pages/supercar-challenge-order-form has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://hankookracetire.com/collections/all and https://hankookracetire.com/blogs/series use the same meta description. A description written for each page earns more clicks.
8 pages without an H1
https://hankookracetire.com/collections/all, https://hankookracetire.com/blogs/series/lucky-dog, https://hankookracetire.com/blogs/series/hankook-commits-to-endurance-racing-with-contingency-program-for-wrl, https://hankookracetire.com/blogs/series/ustcc, https://hankookracetire.com/blogs/series/fara and https://hankookracetire.com/blogs/series/radical-sportscars and 2 others have no <h1> headline, so visitors and search engines get no clear main topic.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 20 found) and read each the way a search engine does.
4 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
16 small tap targets
16 of 46 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 third-party cookies
5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught (in promise) Error: Invalid selector type when creating data client:”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
1 checks passed
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.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Local business without LocalBusiness data
Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.
No analytics detected
No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.
A 11-field form
Your longest form asks for 11 fields (0 required). Every extra field lowers completion.
No opening hours
The homepage shows no opening hours. If customers visit or call, show when.
About 393 words of copy
The homepage carries about 393 words of visible text.
4 checks passed
7 calls to action
The homepage has 7 calls to action, for example “Shop”, “V Max Series Order Form” and “Shop Show menu”.
Direct contact links
Visitors can reach you directly: 3 phone links and 3 email links.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Risk reducer mentioned
A guarantee or risk reducer (money-back, free trial, no credit card or similar) is mentioned on the page.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Ads and 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.
10 cookies set on arrival
10Opening the homepage sets 10 cookies, 1 of them by other companies (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.
20 other companies contacted
Loading the homepage contacts 20 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 hankookracetire.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
Nerdy Form Builder · Tms Prod V 71ff83e · multivariants.com · nerdy-apps.com
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 41 issues on hankookracetire.com, including 17 speed issues, 5 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.