Website review, no card needed
qibbel.com website review
Visit site (opens in a new tab)Reviewed 20 November 202631 issues · 78 checks
This review found 31 issues worth fixing on qibbel.com, 14 of them high impact, across 78 checks. The most urgent: avoid multiple page redirects. 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
79CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 30, 2026 | 1.0 s |
| Jun 6, 2026 | 1.0 s |
| Jun 13, 2026 | 1.0 s |
| Jun 20, 2026 | 1.0 s |
| Jun 27, 2026 | 979 ms |
| Jul 4, 2026 | 1.0 s |
| Jul 11, 2026 | 998 ms |
| Jul 18, 2026 | 1.0 s |
| Jul 25, 2026 | 1.0 s |
| Aug 1, 2026 | 1.0 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.0 s |
| Aug 29, 2026 | 1.0 s |
| Sep 5, 2026 | 1.0 s |
| Sep 12, 2026 | 1.0 s |
| Sep 19, 2026 | 997 ms |
| Sep 26, 2026 | 983 ms |
| Oct 3, 2026 | 949 ms |
| Oct 10, 2026 | 948 ms |
| Oct 17, 2026 | 969 ms |
| Oct 24, 2026 | 965 ms |
| Oct 31, 2026 | 1.0 s |
| Nov 7, 2026 | 999 ms |
| Nov 14, 2026 | 972 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 111 ms |
| Jun 6, 2026 | 113 ms |
| Jun 13, 2026 | 113 ms |
| Jun 20, 2026 | 113 ms |
| Jun 27, 2026 | 114 ms |
| Jul 4, 2026 | 117 ms |
| Jul 11, 2026 | 118 ms |
| Jul 18, 2026 | 119 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 118 ms |
| Aug 8, 2026 | 119 ms |
| Aug 15, 2026 | 119 ms |
| Aug 22, 2026 | 117 ms |
| Aug 29, 2026 | 119 ms |
| Sep 5, 2026 | 116 ms |
| Sep 12, 2026 | 118 ms |
| Sep 19, 2026 | 120 ms |
| Sep 26, 2026 | 118 ms |
| Oct 3, 2026 | 117 ms |
| Oct 10, 2026 | 115 ms |
| Oct 17, 2026 | 112 ms |
| Oct 24, 2026 | 112 ms |
| Oct 31, 2026 | 111 ms |
| Nov 7, 2026 | 110 ms |
| Nov 14, 2026 | 110 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
Speed
Avoid multiple page redirects
7.9 sThe page goes through 1 redirect before it starts loading, costing about 7.9 s. Link and advertise the final URL directly.
Reduce unused JavaScript
1.7 s · 980 KiBAbout 980 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.
Framer CDN adds 1.3 s
1.3 sFramer CDN costs a phone 1.3 s of main-thread work and 6.5 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.
Mobile performance score: 40
40/100Your mobile performance score is 40. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 5.8 s
A phone's processor spends 5.8 s on main-thread work while loading, 3.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
8 third-party services on the page
8 third-party services load with your homepage (Framer CDN, getwally.net and Google Tag Manager and others), adding 8.0 MB and 2.2 s of main-thread time.
Use efficient cache lifetimes
150 ms · 607 KiB31 files are served with short cache lifetimes, so returning visitors download them again (607 KiB).
Improve image delivery
450 ms · 126 KiB3 images could be 126 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.
getwally.net adds 379 ms
379 msgetwally.net costs a phone 379 ms of main-thread work and 758 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 341 ms. During a long task the page ignores taps.
Google Tag Manager adds 261 ms
261 msGoogle Tag Manager costs a phone 261 ms of main-thread work and 332 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,509 HTML elements
The page has 1,509 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Reduce unused CSS
16 KiBAbout 16 KiB of CSS is downloaded but never applied 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 checks passed
Server response: 53 ms
53 msYour server sent the HTML in 53 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.3 s
10.3 sYour largest element takes 10.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 21.9 s
21.9 sThe page becomes fully interactive after 21.9 s. Good is under 3.8 s.
Speed Index: 8.7 s
8.7 sVisually, the page fills in at 8.7 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 933 ms
933 msScripts block taps and scrolling for 933 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 3.1 s
3.1 sThe first text or image appears after 3.1 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 111 ms to 110 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-4%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 1.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
7 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.0 s
1.0 sReal visitors wait 1.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 111 ms
111 msReal visitors wait 111 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.6 s
0.6 sReal visitors see the first content after 0.6 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 319 ms
319 msReal visitors wait 319 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 9.4 MB in 139 requests
9.4 MBYour homepage downloads 9.4 MB in 139 requests on a phone: media 5.6 MB (1), scripts 2.5 MB (84) and images 1.1 MB (29). Under 2 MB keeps phones on slow connections fast.
About 2.7 g of CO₂ per visit
2.67 gBy the Sustainable Web Design model, a visit to your homepage emits about 2.67 g of CO₂e: 320.4 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
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (35 elements)
All page content should be contained by landmarks: 35 elements on the page fail this check, rated moderate by axe-core.
13 links without text
13 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 72 images in the HTML carry an alt attribute.
39 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: 39 passed and 3 failed. 4 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Meta description is short (10 characters)
Your meta description is only 10 characters: “Qibbel.com”. 70 to 160 characters is enough to sell the click.
3 H1 headlines
There are 3 <h1> headlines (“In wind and weather. A safe bicycle seat for ever…”, “Our products” and “Qibbel Air: the lightest bike seat from the Nethe…”). One clear main headline is easier for people and search engines.
4 links crawlers can't follow
4 links have no real href, so search engines can't follow them.
55 internal links, 22 external
The homepage links to 55 pages on qibbel.com and 22 external pages.
6 checks passed
Title: 44 characters
Your title is a healthy 44 characters: “A more joyful cycling experience with Qibbel”.
Canonical URL set
The canonical URL is https://www.qibbel.com/.
Structured data in place
Structured data found: Organization.
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.qibbel.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: 6 of 6 facts
Your Organization JSON-LD gives name, url, logo, sameAs (social profiles), description and contact details.
Text is in the HTML
Your server sends the page's text in the HTML (760 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.qibbel.com/llms.txt (3 KiB, 15 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page is broken
Your homepage links to https://www.qibbel.com/nl/blog/:oUpBVq9_5, which answers with an error. Visitors hit a dead end and search engines drop it.
8 pages share 2 titles
https://www.qibbel.com/en/service-support, https://www.qibbel.com/en/blog, https://www.qibbel.com/en/contact, https://www.qibbel.com/en/about-qibbel, https://www.qibbel.com/en/shop-qibbel and https://www.qibbel.com/en/warranty-1 all use the title “Qibbel.com”, and 1 other title repeat too. 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://www.qibbel.com/en/service-support, https://www.qibbel.com/en/blog, https://www.qibbel.com/en/contact, https://www.qibbel.com/en/about-qibbel, https://www.qibbel.com/en/shop-qibbel and https://www.qibbel.com/en/warranty-1 have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages share a meta description
https://www.qibbel.com/en/accessories and https://www.qibbel.com/en/privacy-cookies-eng use the same meta description. A description written for each page earns more clicks.
2 pages without an H1
https://www.qibbel.com/en/rear-seats and https://www.qibbel.com/en/6-junior have no <h1> headline, so visitors and search engines get no clear main topic.
13 internal pages checked
We fetched 13 pages linked from your homepage and read each the way a search engine does.
3 checks passed
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 12 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”.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
2 checks passed
Tap targets are thumb-sized
19 of 20 tappable elements near the top are at least 24 px.
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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 form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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.
About 475 words of copy
The homepage carries about 475 words of visible text.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Shop Qibbel”.
3 calls to action
The homepage has 3 calls to action, for example “Contact” and “Shop Qibbel”.
Analytics in place
Analytics detected: Google Tag Manager and Google Analytics.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads Google Analytics and Google Tag Manager (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.
2 cookies set on arrival
2Opening the homepage sets 2 cookies (measured from a US location before any click).
15 other companies contacted
Loading the homepage contacts 15 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: Cookiebot
A consent management tool (Cookiebot) loads with the page.
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 qibbel.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- Framer
- Analytics
- Google Analytics | Google Tag Manager
- Hosting
- Framer
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 31 issues on qibbel.com, including 17 speed issues, 3 SEO issues and 1 conversion gap. 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.