Website review, no card needed
eplehuset.no website review
Visit site (opens in a new tab)Reviewed 19 November 202638 issues · 85 checks
This review found 38 issues worth fixing on eplehuset.no, 14 of them high impact, across 85 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
76C- #75,233 of 123,924 reviewed websitesbeats 35%
- #48,208 of 69,719 online storesbeats 26%
- #45,669 of 63,424 Shopify storesbeats 23%
Closest competitors among Shopify stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| 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.6 s |
| Jul 18, 2026 | 1.6 s |
| Jul 25, 2026 | 1.6 s |
| Aug 1, 2026 | 1.5 s |
| Aug 8, 2026 | 1.5 s |
| Aug 15, 2026 | 1.5 s |
| Aug 22, 2026 | 1.6 s |
| Aug 29, 2026 | 1.6 s |
| Sep 5, 2026 | 1.7 s |
| Sep 12, 2026 | 1.7 s |
| Sep 19, 2026 | 1.7 s |
| Sep 26, 2026 | 1.7 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.7 s |
| Nov 7, 2026 | 1.6 s |
| Nov 14, 2026 | 1.6 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 30, 2026 | 131 ms |
| Jun 6, 2026 | 132 ms |
| Jun 13, 2026 | 135 ms |
| Jun 20, 2026 | 137 ms |
| Jun 27, 2026 | 132 ms |
| Jul 4, 2026 | 138 ms |
| Jul 11, 2026 | 137 ms |
| Jul 18, 2026 | 137 ms |
| Jul 25, 2026 | 137 ms |
| Aug 1, 2026 | 130 ms |
| Aug 8, 2026 | 138 ms |
| Aug 15, 2026 | 142 ms |
| Aug 22, 2026 | 146 ms |
| Aug 29, 2026 | 150 ms |
| Sep 5, 2026 | 147 ms |
| Sep 12, 2026 | 147 ms |
| Sep 19, 2026 | 150 ms |
| Sep 26, 2026 | 154 ms |
| Oct 3, 2026 | 161 ms |
| Oct 10, 2026 | 170 ms |
| Oct 17, 2026 | 175 ms |
| Oct 24, 2026 | 183 ms |
| Oct 31, 2026 | 179 ms |
| Nov 7, 2026 | 171 ms |
| Nov 14, 2026 | 163 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
4.8 sThe page goes through 2 redirects before it starts loading, costing about 4.8 s. Link and advertise the final URL directly.
Render-blocking requests
1.5 s22 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.5 s.
Main-thread work: 4.7 s
A phone's processor spends 4.7 s on main-thread work while loading, 2.8 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
3,693 HTML elements
The page has 3,693 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Facebook and Clarity and others), adding 1.8 MB and 884 ms of main-thread time.
Mobile performance score: 51
51/100Your mobile performance score is 51. Pages that score under 90 lose visitors before the first paint.
Reduce unused JavaScript
150 ms · 654 KiBAbout 654 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 150 ms faster on a phone.
Use efficient cache lifetimes
150 ms · 502 KiB31 files are served with short cache lifetimes, so returning visitors download them again (502 KiB).
Google Tag Manager adds 390 ms
390 msGoogle Tag Manager costs a phone 390 ms of main-thread work and 642 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.
14 long tasks on the main thread
14 long tasks block the main thread while loading, the longest for 203 ms. During a long task the page ignores taps.
Document request latency
200 msThe HTML itself could arrive about 200 ms sooner: redirects, a slow server response or missing compression delay everything after it.
Reduce unused CSS
150 ms · 39 KiBAbout 39 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 150 ms faster on a phone.
Improve image delivery
185 KiB5 images could be 185 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Font display
100 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 ms).
Legacy JavaScript
38 KiBPolyfills for old browsers add 38 KiB JavaScript that modern phones do not need.
Minify JavaScript
12 KiB12 KiB could be saved by minifying JavaScript.
Duplicated JavaScript
11 KiB11 KiB JavaScript is shipped twice across bundles.
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: 11 ms
11 msYour server sent the HTML in 11 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.
Largest Contentful Paint: 11.8 s
11.8 sYour largest element takes 11.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image.
Time to Interactive: 29.7 s
29.7 sThe page becomes fully interactive after 29.7 s. Good is under 3.8 s.
Speed Index: 6.7 s
6.7 sVisually, the page fills in at 6.7 s (Speed Index). Good is under 3.4 s.
Real-user INP: 202 ms
202 msReal visitors wait 202 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 27% slower for real visitors
+27%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' tap response (inp) went from 131 ms to 163 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Total Blocking Time: 597 ms
597 msScripts block taps and scrolling for 597 ms in total while the page loads. Good is under 200 ms.
First Contentful Paint: 2.3 s
2.3 sThe first text or image appears after 2.3 s on a phone. Good is under 1.8 s.
3 images without width and height
3 images have no width and height attributes, so the layout jumps as each one loads.
Largest content (LCP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-11-14, real Chrome visitors' largest content (lcp) went from 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
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 CLS: 0.00
0.00For real visitors the layout shifts by 0.00 (75th percentile). Good is under 0.1.
Real-user FCP: 1.1 s
1.1 sReal visitors see the first content after 1.1 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 513 ms
513 msReal visitors wait 513 ms for your server to start answering (75th percentile). Good is under 800 ms.
Cumulative Layout Shift: 0.006
0.006The layout barely moves while loading (CLS 0.006, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 431 requests
5.2 MBYour homepage downloads 5.2 MB in 431 requests on a phone: scripts 2.5 MB (174), other files 914 KiB (127) and images 650 KiB (35). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
Energy_Label_iPhone_Duo_A3720.png 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).
3 images far larger than shown
230 KiB3 images are downloaded at several times the size a phone draws them, for example contact_memo.png at 2,404 px wide, shown at 280 px. Resized copies would save about 230 KiB.
About 1.5 g of CO₂ per visit
1.47 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.47 g of CO₂e: 176.2 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
10 text elements with low contrast
10 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
9 tap targets too small
9 tap targets are too small or too close together to hit reliably with a finger.
ARIA role should be appropriate for the element (6 elements)
ARIA role should be appropriate for the element: 6 elements on the page fail this check, rated minor by axe-core.
Elements marked as presentational should be consistently ignored (1 element)
Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 55 images in the HTML carry an alt attribute.
51 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 55 WCAG 2.2 A/AA and best-practice rules on the phone render: 51 passed and 4 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 long (223 characters)
Your meta description is 223 characters; Google truncates after about 160, so the end of your pitch is cut.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
81 internal links, 5 external
The homepage links to 81 pages on eplehuset.no and 5 external pages.
7 checks passed
One H1 headline
Your main headline reads: “Eplehuset | Det beste stedet for alt fra Apple”.
Title: 46 characters
Your title is a healthy 46 characters: “Eplehuset | Det beste stedet for alt fra Apple”.
Canonical URL set
The canonical URL is https://eplehuset.no/.
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://eplehuset.no/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 (891 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://eplehuset.no/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.
Other pages
1 linked page hidden from search
https://eplehuset.no/pages/brukt-iphone is marked noindex but linked from your homepage. If it is meant to be found, remove the noindex.
2 pages without a meta description
https://eplehuset.no/apps/wishlist and https://eplehuset.no/pages/nyheter have no meta description, so Google writes the search snippet from whatever text it finds.
2 pages without an H1
https://eplehuset.no/apps/wishlist and https://eplehuset.no/collections/macbook-pro 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 37 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.
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.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
17 small tap targets
17 of 71 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Deprecated browser APIs
The page uses 1 deprecated browser API that will stop working in future browsers (“Synchronous `XMLHttpRequest` on the main thread is deprecated because of its detrimental effects to…”).
4 JavaScript errors while loading
4 errors were logged to the browser console while the page loaded, for example “SecurityError: Failed to read a named property 'Function' from 'Window': Blocked a frame with origin "null" from access…”.
Requests the geolocation permission on page load
Requests the geolocation permission on page load.
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 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.
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 700 words of copy
The homepage carries about 700 words of visible text.
2 checks passed
6 short forms
6 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager and Microsoft Clarity.
Privacy and tracking
10 trackers load before any consent
10Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Klaviyo and 5 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.
35 cookies set on arrival
35Opening the homepage sets 35 cookies, 5 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.
47 other companies contacted
Loading the homepage contacts 47 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 eplehuset.no, 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 8 apps. Each one is code from another company running for your shoppers.
Apps your storefront loads
Microsoft Clarity · Sc Easy Redirects · Klaviyo Email Marketing Sms · Punchout · Swish Wishlist King · Back In Stock · amazonaws.com · trymimir.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
- Analytics
- Google Tag Manager | Microsoft Clarity
- Hosting
- Shopify
Company
- Employees
- 35
- Founded
- 2002
- Headquarters
- Trondheim
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 eplehuset.no, including 18 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.