Website review, no card needed
semihandmade.com website review
Visit site (opens in a new tab)Reviewed 20 November 202635 issues · 80 checks
This review found 35 issues worth fixing on semihandmade.com, 11 of them high impact, across 80 checks. The most urgent: hcaptcha.com adds 1.1 s. 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
80B- #47,149 of 120,280 reviewed websitesbeats 55%
- #31,324 of 68,120 online storesbeats 48%
- #30,124 of 62,083 Shopify storesbeats 45%
Closest competitors among Shopify stores
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 | 1.1 s |
| Jul 4, 2026 | 1.1 s |
| Jul 11, 2026 | 1.1 s |
| Jul 18, 2026 | 1.1 s |
| Jul 25, 2026 | 1.1 s |
| Aug 1, 2026 | 1.1 s |
| Aug 8, 2026 | 1.0 s |
| Aug 15, 2026 | 1.0 s |
| Aug 22, 2026 | 1.1 s |
| Aug 29, 2026 | 1.1 s |
| Sep 5, 2026 | 1.1 s |
| Sep 12, 2026 | 1.1 s |
| Sep 19, 2026 | 1.1 s |
| Sep 26, 2026 | 1.1 s |
| Oct 3, 2026 | 1.0 s |
| Oct 10, 2026 | 996 ms |
| Oct 17, 2026 | 997 ms |
| Oct 24, 2026 | 971 ms |
| Oct 31, 2026 | 973 ms |
| Nov 7, 2026 | 949 ms |
| Nov 14, 2026 | 912 ms |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 95 ms |
| Jun 6, 2026 | 96 ms |
| Jun 13, 2026 | 99 ms |
| Jun 20, 2026 | 102 ms |
| Jun 27, 2026 | 104 ms |
| Jul 4, 2026 | 105 ms |
| Jul 11, 2026 | 104 ms |
| Jul 18, 2026 | 104 ms |
| Jul 25, 2026 | 104 ms |
| Aug 1, 2026 | 103 ms |
| Aug 8, 2026 | 104 ms |
| Aug 15, 2026 | 104 ms |
| Aug 22, 2026 | 104 ms |
| Aug 29, 2026 | 106 ms |
| Sep 5, 2026 | 105 ms |
| Sep 12, 2026 | 104 ms |
| Sep 19, 2026 | 104 ms |
| Sep 26, 2026 | 102 ms |
| Oct 3, 2026 | 103 ms |
| Oct 10, 2026 | 104 ms |
| Oct 17, 2026 | 106 ms |
| Oct 24, 2026 | 108 ms |
| Oct 31, 2026 | 107 ms |
| Nov 7, 2026 | 109 ms |
| Nov 14, 2026 | 108 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.7 s
1.5 s
2.2 s
2.9 s
3.6 s
4.4 s
5.1 s
5.8 s
Speed
hcaptcha.com adds 1.1 s
1.1 shcaptcha.com costs a phone 1.1 s of main-thread work and 1.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: 37
37/100Your mobile performance score is 37. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 8.4 s
A phone's processor spends 8.4 s on main-thread work while loading, 3.8 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 (hcaptcha.com, frontapp.com and Hotjar and others), adding 4.3 MB and 2.5 s of main-thread time.
Reduce unused JavaScript
600 ms · 1.2 MBAbout 1.2 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 600 ms faster on a phone.
frontapp.com adds 474 ms
474 msfrontapp.com costs a phone 474 ms of main-thread work and 682 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.
Use efficient cache lifetimes
490 KiB21 files are served with short cache lifetimes, so returning visitors download them again (490 KiB).
16 long tasks on the main thread
16 long tasks block the main thread while loading, the longest for 488 ms. During a long task the page ignores taps.
Improve image delivery
381 KiB8 images could be 381 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Render-blocking requests
300 ms7 files block the first paint until they finish downloading. Deferring or inlining them could save about 300 ms.
Hotjar adds 284 ms
284 msHotjar costs a phone 284 ms of main-thread work and 68 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 158 ms
158 msShopify costs a phone 158 ms of main-thread work and 1.3 MB 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.
Klaviyo adds 165 ms
165 msKlaviyo costs a phone 165 ms of main-thread work and 320 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,564 HTML elements
The page has 1,564 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Legacy JavaScript
89 KiBPolyfills for old browsers add 89 KiB JavaScript that modern phones do not need.
Reduce unused CSS
75 KiBAbout 75 KiB of CSS is downloaded but never applied on this page.
Minify JavaScript
8 KiB8 KiB could be saved by minifying JavaScript.
Minify CSS
7 KiB7 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: 18 ms
18 msYour server sent the HTML in 18 ms, well inside Google's 600 ms guideline.
Core Web Vitals
First Contentful Paint: 8.2 s
8.2 sThe first text or image appears after 8.2 s on a phone. Good is under 1.8 s.
Time to Interactive: 38.3 s
38.3 sThe page becomes fully interactive after 38.3 s. Good is under 3.8 s.
Speed Index: 14.0 s
14.0 sVisually, the page fills in at 14.0 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 8.2 s
8.2 sYour largest element takes 8.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “To send IKEA or custom plans for your kitchen, bathroom, or…”.
Total Blocking Time: 764 ms
764 msScripts block taps and scrolling for 764 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 14% slower for real visitors
+14%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 95 ms to 108 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-9%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.0 s to 0.9 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: 0.8 s
0.8 sReal visitors wait 0.8 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 126 ms
126 msReal visitors wait 126 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.8 s
0.8 sReal visitors see the first content after 0.8 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 348 ms
348 msReal visitors wait 348 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: 6.9 MB in 605 requests
6.9 MBYour homepage downloads 6.9 MB in 605 requests on a phone: scripts 3.4 MB (227), other files 1.5 MB (277) and HTML 802 KiB (5). Under 2 MB keeps phones on slow connections fast.
About 2.0 g of CO₂ per visit
1.95 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.95 g of CO₂e: 234.4 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
Accessibility
Delayed refresh under 20 hours must not be used (1 element)
Delayed refresh under 20 hours must not be used: 1 element on the page fails this check, rated critical 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.
33 text elements with low contrast
33 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
21 tap targets too small
21 tap targets are too small or too close together to hit reliably with a finger.
Elements with role="dialog" or role="alertdialog" do not have accessible names.
Elements with role="dialog" or role="alertdialog" do not have accessible names. (1 element).
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 83 images in the HTML carry an alt attribute.
20 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 23 WCAG 2.2 A/AA and best-practice rules on the phone render: 20 passed and 3 failed. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
2 links with vague text
2 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
129 internal links, 14 external
The homepage links to 129 pages on semihandmade.com and 14 external pages.
7 checks passed
Meta description: 129 characters
Your meta description is 129 characters: “Reimagine your kitchen, bathroom & living spaces with affordable, designer-favorite cabinets and cabinet doors from Sem…”.
One H1 headline
Your main headline reads: “The Black Friday Sale is On!”.
Title: 47 characters
Your title is a healthy 47 characters: “Cabinets & Custom Doors for Ikea | Semihandmade”.
Canonical URL set
The canonical URL is https://www.semihandmade.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.semihandmade.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.
2 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.
llms.txt published
The site publishes https://www.semihandmade.com/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
6 pages share a meta description
https://www.semihandmade.com/products/select-5in-cabinet-pull-by-emtek-grouped, https://www.semihandmade.com/products/select-12in-cabinet-pull-by-emtek-grouped and https://www.semihandmade.com/products/select-6in-cabinet-pull-by-emtek-grouped use the same meta description. A description written for each page earns more clicks.
1 page without an H1
https://www.semihandmade.com/pages/design-services-1 has 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 58 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 15 pages that loaded have a meta description.
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 15 pages that loaded have a <title>.
Best practices
3 JavaScript errors while loading
3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 429 ()”.
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 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 10 words
The homepage has only about 10 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.
4 checks passed
22 calls to action
The homepage has 22 calls to action, for example “Shop Now!”, “Learn More” and “Pricing Examples”.
3 short forms
3 short forms (2 fields at most) are right on the homepage, asking for an email.
Social proof on the page
Social proof on the homepage: 34 testimonial or review blocks and a star rating.
Analytics in place
Analytics detected: Google Tag Manager, Microsoft Clarity and Hotjar.
Privacy and tracking
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.
2 other companies contacted
Loading the homepage contacts 2 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
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 semihandmade.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- E-commerce
- Shopify;Shopify Local Pickup;Shopify Plus;Shopify POS
- Hosting
- Shopify
Company
- Headquarters
- Monrovia
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 35 issues on semihandmade.com, including 19 speed issues, 2 SEO issues and 3 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.