Website review, no card needed
lekkerbikes.us website review
Visit site (opens in a new tab)Reviewed 9 November 202632 issues · 67 checks
This review found 32 issues worth fixing on lekkerbikes.us, 11 of them high impact, across 67 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
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
1.2 s · 257 KiBAbout 257 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.2 s faster on a phone.
Mobile performance score: 56
56/100Your mobile performance score is 56. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
750 ms · 238 KiB10 files are served with short cache lifetimes, so returning visitors download them again (238 KiB).
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 836 KiB and 668 ms of main-thread time.
Improve image delivery
360 KiB1 image could be 360 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 320 ms
320 msGoogle Tag Manager costs a phone 320 ms of main-thread work and 355 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.
Render-blocking requests
350 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 350 ms.
5 long tasks on the main thread
5 long tasks block the main thread while loading, the longest for 209 ms. During a long task the page ignores taps.
Legacy JavaScript
150 ms · 31 KiBPolyfills for old browsers add 31 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 150 ms faster on a phone.
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.
2 checks passed
Main-thread work: 1.4 s
A phone's processor spends 1.4 s on main-thread work while loading, 856 ms of it running JavaScript. That is comfortably low.
Server response: 5 ms
5 msYour server sent the HTML in 5 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 11.1 s
11.1 sYour largest element takes 11.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 11.2 s
11.2 sThe page becomes fully interactive after 11.2 s. Good is under 3.8 s.
Speed Index: 6.2 s
6.2 sVisually, the page fills in at 6.2 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 373 ms
373 msScripts block taps and scrolling for 373 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.2 s
2.2 sThe first text or image appears after 2.2 s on a phone. Good is under 1.8 s.
Not enough real-visitor data yet
Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.
1 checks passed
Cumulative Layout Shift: 0.098
0.098The layout barely moves while loading (CLS 0.098, good is under 0.1).
Images and page weight
Page weight: 2.2 MB in 146 requests
2.2 MBYour homepage downloads 2.2 MB in 146 requests on a phone: scripts 937 KiB (57), other files 674 KiB (77) and images 452 KiB (4). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
conventional-jordaan-range_7b8ebb51-d920-4713-b04a-0fe8e7402 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).
About 0.6 g of CO₂ per visit
0.63 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.63 g of CO₂e: 75.9 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
2 buttons without a name
2 buttons have no accessible name, so screen readers announce just “button”.
5 images without alt text
5 images have no alt text, which hurts accessibility and image search.
Page should contain a level-one heading (1 element)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
All page content should be contained by landmarks (1 element)
All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.
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.
1 checks passed
38 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 42 WCAG 2.2 A/AA and best-practice rules on the phone render: 38 passed and 4 failed. 1 more 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.
Structured data has 2 problems
Structured data found ((untyped)) but with 2 problems, for example “untyped block: missing @context (expected "https://schema.org")”.
6 internal links, 1 external
The homepage links to 6 pages on lekkerbikes.us and 1 external page.
6 checks passed
Meta description: 151 characters
Your meta description is 151 characters: “Discover the LEKKER Bikes range: combining style, comfort, and composed to perfection. Rediscover the joy of riding a b…”.
Title: 64 characters
Your title is a healthy 64 characters: “Premium Dutch Bikes | Shop now | LEKKER Bikes – Lekker Bikes USA”.
Canonical URL set
The canonical URL is https://www.lekkerbikes.us/.
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.lekkerbikes.us/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.
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.
Text is in the HTML
Your server sends the page's text in the HTML (259 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.lekkerbikes.us/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 page points its canonical at the homepage
https://www.lekkerbikes.us/pages/privacy-policy declares the homepage as its canonical URL, which tells Google it is a copy of the homepage and keeps it out of search results. A site-wide template setting usually causes this.
2 pages share a title
/ and https://www.lekkerbikes.us/pages/privacy-policy all use the title “Premium Dutch Bikes | Shop now | LEKKER Bikes – Lekker Bikes USA”. Search engines can't tell which page to show for a search, so each competes with the others.
1 page without a meta description
https://www.lekkerbikes.us/collections/all has no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://www.lekkerbikes.us/collections/all and https://www.lekkerbikes.us/pages/privacy-policy have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.lekkerbikes.us/collections/all 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.
3 internal pages checked
We fetched 3 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Linked pages load
2 pages of 3 loaded without an error (the rest turned automated requests away).
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 2 pages that loaded have a <title>.
Best practices
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Uncaught ReferenceError: convert is not defined”.
2 checks passed
Tap targets are thumb-sized
7 of 7 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.
No calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
Only about 204 words
The homepage has only about 204 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.
3 checks passed
1 short form
A short form (0 fields at most) is right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager, Meta Pixel and Microsoft Clarity.
Direct contact links
Visitors can reach you directly: 0 phone links and 1 email link.
Privacy and tracking
6 trackers load before any consent
6Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 1 more (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.
14 cookies set on arrival
14Opening the homepage sets 14 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.
18 other companies contacted
Loading the homepage contacts 18 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 lekkerbikes.us, 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 2 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Klaviyo Email Marketing Sms · Ta Labels Badges
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
- jQuery
- E-commerce
- Shopify
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 32 issues on lekkerbikes.us, including 12 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.