Website review, no card needed
bybiehl.com website review
Visit site (opens in a new tab)Reviewed 9 November 202638 issues · 89 checks
This review found 38 issues worth fixing on bybiehl.com, 13 of them high impact, across 89 checks. The most urgent: render-blocking 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
85B- #16,084 of 118,576 reviewed websitesbeats 82%
- #10,221 of 67,354 online storesbeats 79%
- #9,933 of 61,413 Shopify storesbeats 78%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 23, 2026 | 1.8 s |
| May 30, 2026 | 1.8 s |
| Jun 6, 2026 | 1.9 s |
| Jun 13, 2026 | 2.0 s |
| Jun 20, 2026 | 2.0 s |
| Jun 27, 2026 | 1.9 s |
| Jul 4, 2026 | 1.9 s |
| Jul 11, 2026 | 1.9 s |
| Jul 18, 2026 | 1.8 s |
| Jul 25, 2026 | 1.8 s |
| Aug 1, 2026 | 1.7 s |
| Aug 8, 2026 | 1.7 s |
| Aug 15, 2026 | 1.7 s |
| Aug 22, 2026 | 1.7 s |
| Aug 29, 2026 | 1.8 s |
| Sep 5, 2026 | 1.8 s |
| Sep 12, 2026 | 1.8 s |
| Sep 19, 2026 | 1.8 s |
| Sep 26, 2026 | 1.8 s |
| Oct 3, 2026 | 1.7 s |
| Oct 10, 2026 | 1.7 s |
| Oct 17, 2026 | 1.7 s |
| Oct 24, 2026 | 1.7 s |
| Oct 31, 2026 | 1.8 s |
| Nov 7, 2026 | 1.7 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 23, 2026 | 168 ms |
| May 30, 2026 | 180 ms |
| Jun 6, 2026 | 197 ms |
| Jun 13, 2026 | 198 ms |
| Jun 20, 2026 | 202 ms |
| Jun 27, 2026 | 180 ms |
| Jul 4, 2026 | 167 ms |
| Jul 11, 2026 | 163 ms |
| Jul 18, 2026 | 165 ms |
| Jul 25, 2026 | 170 ms |
| Aug 1, 2026 | 161 ms |
| Aug 8, 2026 | 199 ms |
| Aug 15, 2026 | 212 ms |
| Aug 22, 2026 | 214 ms |
| Aug 29, 2026 | 226 ms |
| Sep 5, 2026 | 194 ms |
| Sep 12, 2026 | 172 ms |
| Sep 19, 2026 | 170 ms |
| Sep 26, 2026 | 180 ms |
| Oct 3, 2026 | 195 ms |
| Oct 10, 2026 | 193 ms |
| Oct 17, 2026 | 196 ms |
| Oct 24, 2026 | 191 ms |
| Oct 31, 2026 | 183 ms |
| Nov 7, 2026 | 184 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.9 s
1.8 s
2.6 s
3.5 s
4.4 s
5.3 s
6.2 s
7.0 s
Speed
Render-blocking requests
1.6 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.6 s.
Main-thread work: 4.9 s
A phone's processor spends 4.9 s on main-thread work while loading, 1.6 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,897 HTML elements
The page has 3,897 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Mobile performance score: 58
58/100Your mobile performance score is 58. Pages that score under 90 lose visitors before the first paint.
Improve image delivery
450 ms · 491 KiB18 images could be 491 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.
8 third-party services on the page
8 third-party services load with your homepage (Shopify, Clarity and Klaviyo and others), adding 894 KiB and 684 ms of main-thread time.
Reduce unused CSS
450 ms · 104 KiBAbout 104 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 450 ms faster on a phone.
Shopify adds 303 ms
303 msShopify costs a phone 303 ms of main-thread work and 443 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.
Reduce unused JavaScript
281 KiBAbout 281 KiB of JavaScript is downloaded but never used on this page.
10 long tasks on the main thread
10 long tasks block the main thread while loading, the longest for 168 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
91 KiB12 files are served with short cache lifetimes, so returning visitors download them again (91 KiB).
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
28 KiBPolyfills for old browsers add 28 KiB JavaScript that modern phones do not need.
Minify CSS
6 KiB6 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: 12 ms
12 msYour server sent the HTML in 12 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 10.9 s
10.9 sYour largest element takes 10.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 22.8 s
22.8 sThe page becomes fully interactive after 22.8 s. Good is under 3.8 s.
Speed Index: 10.4 s
10.4 sVisually, the page fills in at 10.4 s (Speed Index). Good is under 3.4 s.
First Contentful Paint: 3.0 s
3.0 sThe first text or image appears after 3.0 s on a phone. Good is under 1.8 s.
Tap response (INP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' tap response (inp) went from 168 ms to 184 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-6%Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
8 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.7 s
1.7 sReal visitors wait 1.7 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 184 ms
184 msReal visitors wait 184 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: 1.4 s
1.4 sReal visitors see the first content after 1.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 658 ms
658 msReal visitors wait 658 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 175 ms
175 msScripts block the page for only 175 ms while loading. Good is under 200 ms.
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 10.9 MB in 360 requests
10.9 MBYour homepage downloads 10.9 MB in 360 requests on a phone: images 6.0 MB (100), media 2.5 MB (1) and scripts 965 KiB (87). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
IMG_7005.heic 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).
5 images far larger than shown
159 KiB5 images are downloaded at several times the size a phone draws them, for example EmilyHoopChestnut_GP.png at 900 px wide, shown at 251 px. Resized copies would save about 159 KiB.
1 image below the first screen load straight away
1 image further down the page (20 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 3.1 g of CO₂ per visit
3.10 gBy the Sustainable Web Design model, a visit to your homepage emits about 3.10 g of CO₂e: 371.9 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images use modern formats
Every sizeable image is WebP, AVIF or SVG.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
Scrollable region must have keyboard access (6 elements)
Scrollable region must have keyboard access: 6 elements on the page fail this check, rated serious by axe-core.
5 tap targets too small
5 tap targets are too small or too close together to hit reliably with a finger.
17 images without alt text
17 images have no alt text, which hurts accessibility and image search.
All page content should be contained by landmarks (3 elements)
All page content should be contained by landmarks: 3 elements on the page fail this check, rated moderate by axe-core.
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (2 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 2 elements on the page fail this check, rated moderate by axe-core.
Contentinfo landmark should not be contained in another landmark (1 element)
Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one banner landmark (1 element)
Document should not have more than one banner landmark: 1 element on the page fails this check, rated moderate by axe-core.
Document should not have more than one contentinfo landmark (1 element)
Document should not have more than one contentinfo landmark: 1 element on the page fails this check, rated moderate by axe-core.
51 links without text
51 visible links have no text or label, so screen readers cannot say where they go.
ARIA role should be appropriate for the element (1 element)
ARIA role should be appropriate for the element: 1 element on the page fails this check, rated minor 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.
Headings skip levels
Headings skip levels (h3 → h5, h2 → h5 and h2 → h5), which makes the page harder to scan with a screen reader.
1 checks passed
48 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 61 WCAG 2.2 A/AA and best-practice rules on the phone render: 48 passed and 13 failed. 3 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.
Title is long (80 characters)
Your title is 80 characters, so Google will cut it off around 60: “byBIEHL® - Timeless jewelry designed in Copenhagen since 2010 – byBiehl® Danmark”.
205 internal links, 11 external
The homepage links to 205 pages on bybiehl.com and 11 external pages.
6 checks passed
Meta description: 126 characters
Your meta description is 126 characters: “Scandinavian design in 100% recycled metal. Earrings, rings, charms, and 14K solid gold. Free shipping on orders over D…”.
Canonical URL set
The canonical URL is https://www.bybiehl.com/en-eu.
Structured data in place
Structured data found: Organization and WebSite.
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.bybiehl.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 (1,504 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.bybiehl.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
10 pages share 5 titles
https://www.bybiehl.com/collections/oreringe and https://www.bybiehl.com/en-eu/collections/earrings all use the title “Earrings and Stud Earrings - Danish Jewelry in Elegant Design - Free …”, and 4 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.
13 pages share a meta description
https://www.bybiehl.com/collections/oreringe and https://www.bybiehl.com/en-eu/collections/earrings use the same meta description. A description written for each page earns more clicks.
6 links to non-canonical URLs
Your homepage links to 6 pages by a URL that isn't their canonical one, for example https://www.bybiehl.com/collections/oreringe, whose canonical is https://www.bybiehl.com/en-eu/collections/earrings. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
4 pages without an H1
https://www.bybiehl.com/en-eu/pages/reviews, https://www.bybiehl.com/en-eu/pages/inspiration, https://www.bybiehl.com/en-eu/pages/gifts and https://www.bybiehl.com/en-eu/pages/collections 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 103 found) and read each the way a search engine does.
4 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
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
14 small tap targets
14 of 69 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
5 JavaScript errors while loading
5 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”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
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.
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 664 words of copy
The homepage carries about 664 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “SHOP ALL” and “SHOP NOW”.
24 calls to action
The homepage has 24 calls to action, for example “SHOP ALL”, “Shop all” and “FAQ/Contact Us”.
23 short forms
23 short forms (5 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 50 testimonial or review blocks, a star rating, 1 trust badge and “over 2,300 reviews”.
Analytics in place
Analytics detected: Microsoft Clarity.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Meta Pixel and 3 mores (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.
12 cookies set on arrival
12Opening the homepage sets 12 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.
45 other companies contacted
Loading the homepage contacts 45 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 bybiehl.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 13 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Geo Pro Geolocation · Microsoft Clarity · Hulk Form Builder · Sami Product Labels · Klaviyo Email Marketing Sms · Zepto Product Personalizer · Deluxe Customer Accounts · Easylocation · Propel Appointments · Bestpush · Gift Box Builder · stamped.io · amazonaws.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
- Framework
- Bootstrap
- E-commerce
- Shopify
- Analytics
- Microsoft Clarity
- Hosting
- Shopify
Company
- Headquarters
- Hellerup
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 38 issues on bybiehl.com, including 13 speed issues, 2 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.