Website review, no card needed
hrd2kll.com website review
Visit site (opens in a new tab)Reviewed 7 November 202634 issues · 80 checks
This review found 34 issues worth fixing on hrd2kll.com, 7 of them high impact, across 80 checks. The most urgent: page weight: 7.5 MB in 338 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
81B- #40,326 of 119,930 reviewed websitesbeats 61%
- #26,875 of 67,979 online storesbeats 54%
- #25,916 of 61,955 Shopify storesbeats 51%
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.7 s |
| May 30, 2026 | 1.6 s |
| Jun 6, 2026 | 1.6 s |
| Jun 13, 2026 | 1.6 s |
| Jun 20, 2026 | 1.6 s |
| Jun 27, 2026 | 1.6 s |
| Jul 4, 2026 | 1.6 s |
| Jul 11, 2026 | 1.7 s |
| Jul 18, 2026 | 1.7 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.6 s |
| Aug 8, 2026 | 1.6 s |
| Aug 15, 2026 | 1.6 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.5 s |
| Sep 5, 2026 | 1.5 s |
| Sep 12, 2026 | 1.5 s |
| Sep 19, 2026 | 1.6 s |
| Sep 26, 2026 | 1.6 s |
| Oct 3, 2026 | 1.5 s |
| Oct 10, 2026 | 1.6 s |
| Oct 17, 2026 | 1.5 s |
| Oct 24, 2026 | 1.6 s |
| Oct 31, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 111 ms |
| May 23, 2026 | 105 ms |
| May 30, 2026 | 104 ms |
| Jun 6, 2026 | 90 ms |
| Jun 13, 2026 | 87 ms |
| Jun 20, 2026 | 87 ms |
| Jun 27, 2026 | 87 ms |
| Jul 4, 2026 | 87 ms |
| Sep 19, 2026 | 84 ms |
| Sep 26, 2026 | 84 ms |
| Oct 3, 2026 | 85 ms |
| Oct 10, 2026 | 89 ms |
| Oct 31, 2026 | 104 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.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
580 ms · 902 KiBAbout 902 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 580 ms faster on a phone.
Mobile performance score: 71
71/100Your mobile performance score is 71. Pages that score under 90 lose visitors before the first paint.
8 third-party services on the page
8 third-party services load with your homepage (route.com, PayPal and Shopify and others), adding 1.7 MB and 806 ms of main-thread time.
Use efficient cache lifetimes
955 KiB15 files are served with short cache lifetimes, so returning visitors download them again (955 KiB).
Render-blocking requests
500 ms3 files block the first paint until they finish downloading. Deferring or inlining them could save about 500 ms.
route.com adds 406 ms
406 msroute.com costs a phone 406 ms of main-thread work and 717 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.
8 long tasks on the main thread
8 long tasks block the main thread while loading, the longest for 371 ms. During a long task the page ignores taps.
Main-thread work: 3.7 s
A phone's processor spends 3.7 s on main-thread work while loading, 1.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
PayPal adds 219 ms
219 msPayPal costs a phone 219 ms of main-thread work and 389 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.
1,734 HTML elements
The page has 1,734 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Shopify adds 105 ms
105 msShopify costs a phone 105 ms of main-thread work and 378 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.
Duplicated JavaScript
104 KiB104 KiB JavaScript is shipped twice across bundles.
Reduce unused CSS
92 KiBAbout 92 KiB of CSS is downloaded but never applied on this page.
Improve image delivery
81 KiB4 images could be 81 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Minify JavaScript
40 KiB40 KiB could be saved by minifying JavaScript.
Legacy JavaScript
23 KiBPolyfills for old browsers add 23 KiB JavaScript that modern phones do not need.
Minify CSS
19 KiB19 KiB could be saved by minifying CSS.
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
Time to Interactive: 20.3 s
20.3 sThe page becomes fully interactive after 20.3 s. Good is under 3.8 s.
Largest Contentful Paint: 5.7 s
5.7 sYour largest element takes 5.7 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below.
Total Blocking Time: 323 ms
323 msScripts block taps and scrolling for 323 ms in total while the page loads. Good is under 200 ms.
Speed Index: 3.5 s
3.5 sVisually, the page fills in at 3.5 s (Speed Index). Good is under 3.4 s.
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.6 s 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.4 s
1.4 sReal visitors wait 1.4 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 95 ms
95 msReal visitors wait 95 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 0.7 s
0.7 sReal visitors see the first content after 0.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 455 ms
455 msReal visitors wait 455 ms for your server to start answering (75th percentile). Good is under 800 ms.
Tap response (INP) got 11% faster for real visitors
-11%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 111 ms to 104 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0.026
0.026The layout barely moves while loading (CLS 0.026, good is under 0.1).
First Contentful Paint: 0.9 s
0.9 sThe first text or image appears after 0.9 s, inside the 1.8 s “good” threshold.
Images and page weight
Page weight: 7.5 MB in 338 requests
7.5 MBYour homepage downloads 7.5 MB in 338 requests on a phone: media 3.9 MB (2), scripts 1.7 MB (139) and other files 966 KiB (162). Under 2 MB keeps phones on slow connections fast.
3 images below the first screen load straight away
3 images further down the page (130 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 2.1 g of CO₂ per visit
2.14 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.14 g of CO₂e: 256.2 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 tap target too small
1 tap target is too small or too close together to hit reliably with a finger.
1 image without alt text
1 image has no alt text, which hurts accessibility and image search.
4 links without text
4 visible links have no text or label, so screen readers cannot say where they go.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (12 elements).
1 checks passed
43 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 46 WCAG 2.2 A/AA and best-practice rules on the phone render: 43 passed and 3 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 (10 characters)
Your title is only 10 characters: “HRD // KLL”. Between 30 and 65 characters leaves room to say what you do and for whom.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
Meta description is long (297 characters)
Your meta description is 297 characters; Google truncates after about 160, so the end of your pitch is cut.
3 links crawlers can't follow
3 links have no real href, so search engines can't follow them.
43 internal links, 0 external
The homepage links to 43 pages on hrd2kll.com and 0 external pages.
5 checks passed
One H1 headline
Your main headline reads: “.logo--image { height: auto; width: 273px; } @media only screen and (max-width: 767px) { .logo--image { width: 273px; }…”.
Canonical URL set
The canonical URL is https://www.hrd2kll.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.hrd2kll.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.hrd2kll.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 pages without a meta description
https://www.hrd2kll.com/collections/menswear, https://www.hrd2kll.com/collections/womenswear, https://www.hrd2kll.com/collections/hats and https://www.hrd2kll.com/collections/accessories have no meta description, so Google writes the search snippet from whatever text it finds.
5 pages without an H1
https://www.hrd2kll.com/collections/nutrition, https://www.hrd2kll.com/collections/menswear, https://www.hrd2kll.com/collections/womenswear, https://www.hrd2kll.com/collections/hats and https://www.hrd2kll.com/collections/accessories 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 30 found) and read each the way a search engine does.
5 checks passed
Linked pages load
7 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.
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 7 pages that loaded have a <title>.
Best practices
3 small tap targets
3 of 7 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 “Failed to load resource: net::ERR_FAILED”.
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.
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 70 words
The homepage has only about 70 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
6 calls to action
The homepage has 6 calls to action, for example “SHOP”, “SUBSCRIBE” and “Contact Information”.
3 short forms
3 short forms (1 field at most) are right on the homepage.
Privacy and tracking
4 trackers load before any consent
4Before a visitor clicks anything, the page loads Amplitude, 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.
11 cookies set on arrival
11Opening the homepage sets 11 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.
22 other companies contacted
Loading the homepage contacts 22 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 hrd2kll.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 7 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Regios Discounts · Seal Subscriptions · stamped.io · goaffpro.com · route.com · postscript.io · useamp.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 34 issues on hrd2kll.com, including 15 speed issues, 4 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.