Website review, no card needed
optimera.se website review
Visit site (opens in a new tab)Reviewed 4 November 202636 issues · 85 checks
This review found 36 issues worth fixing on optimera.se, 8 of them high impact, across 85 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
76CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 16, 2026 | 2.0 s |
| May 30, 2026 | 2.0 s |
| Jun 6, 2026 | 2.0 s |
| Jun 13, 2026 | 2.1 s |
| Jun 20, 2026 | 2.1 s |
| Jun 27, 2026 | 2.1 s |
| Jul 4, 2026 | 2.1 s |
| Jul 11, 2026 | 2.1 s |
| Jul 18, 2026 | 2.1 s |
| Jul 25, 2026 | 2.0 s |
| Aug 1, 2026 | 2.0 s |
| Aug 8, 2026 | 2.0 s |
| Aug 15, 2026 | 2.0 s |
| Aug 22, 2026 | 2.0 s |
| Aug 29, 2026 | 2.1 s |
| Sep 5, 2026 | 2.1 s |
| Sep 12, 2026 | 2.1 s |
| Sep 19, 2026 | 2.1 s |
| Sep 26, 2026 | 2.0 s |
| Oct 3, 2026 | 2.1 s |
| Oct 10, 2026 | 2.1 s |
| Oct 17, 2026 | 2.2 s |
| Oct 24, 2026 | 2.2 s |
| Oct 31, 2026 | 2.2 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 16, 2026 | 164 ms |
| May 30, 2026 | 169 ms |
| Jun 6, 2026 | 167 ms |
| Jun 13, 2026 | 165 ms |
| Jun 20, 2026 | 163 ms |
| Jun 27, 2026 | 162 ms |
| Jul 4, 2026 | 162 ms |
| Jul 11, 2026 | 162 ms |
| Jul 18, 2026 | 162 ms |
| Jul 25, 2026 | 161 ms |
| Aug 1, 2026 | 162 ms |
| Aug 8, 2026 | 161 ms |
| Aug 15, 2026 | 158 ms |
| Aug 22, 2026 | 161 ms |
| Aug 29, 2026 | 155 ms |
| Sep 5, 2026 | 157 ms |
| Sep 12, 2026 | 161 ms |
| Sep 19, 2026 | 161 ms |
| Sep 26, 2026 | 165 ms |
| Oct 3, 2026 | 170 ms |
| Oct 10, 2026 | 169 ms |
| Oct 17, 2026 | 171 ms |
| Oct 24, 2026 | 170 ms |
| Oct 31, 2026 | 170 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.4 s
2.1 s
2.8 s
3.5 s
4.2 s
4.9 s
5.7 s
Speed
Render-blocking requests
1.4 s9 files block the first paint until they finish downloading. Deferring or inlining them could save about 1.4 s.
Mobile performance score: 59
59/100Your mobile performance score is 59. Pages that score under 90 lose visitors before the first paint.
Use efficient cache lifetimes
300 ms · 551 KiB69 files are served with short cache lifetimes, so returning visitors download them again (551 KiB).
Improve image delivery
500 ms · 303 KiB11 images could be 303 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 500 ms faster on a phone.
Reduce unused JavaScript
396 KiBAbout 396 KiB of JavaScript is downloaded but never used on this page.
7 third-party services on the page
7 third-party services load with your homepage (Google Tag Manager, Google Maps and Optanon and others), adding 1.7 MB and 147 ms of main-thread time.
ctfassets.net adds 0 ms
0 msctfassets.net costs a phone 0 ms of main-thread work and 598 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.
Google Fonts adds 0 ms
0 msGoogle Fonts costs a phone 0 ms of main-thread work and 454 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 137 ms. During a long task the page ignores taps.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Reduce unused CSS
45 KiBAbout 45 KiB of CSS is downloaded but never applied on this page.
Legacy JavaScript
18 KiBPolyfills for old browsers add 18 KiB JavaScript that modern phones do not need.
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.3 s
A phone's processor spends 1.3 s on main-thread work while loading, 690 ms of it running JavaScript. That is comfortably low.
Server response: 533 ms
533 msYour server sent the HTML in 533 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: 8.1 s
8.1 sYour largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Bygghandel för proffs …”.
Time to Interactive: 14.7 s
14.7 sThe page becomes fully interactive after 14.7 s. Good is under 3.8 s.
Speed Index: 8.3 s
8.3 sVisually, the page fills in at 8.3 s (Speed Index). Good is under 3.4 s.
Real-user CLS: 0.16
0.16For real visitors the layout shifts by 0.16 (75th percentile). Good is under 0.1.
First Contentful Paint: 2.7 s
2.7 sThe first text or image appears after 2.7 s on a phone. Good is under 1.8 s.
Cumulative Layout Shift: 0.131
0.131The layout shifts by 0.131 while loading, so content jumps under the reader's thumb. Good is under 0.1.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Tap response (INP) held steady for real visitors
+2%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 164 ms to 170 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) got 10% slower for real visitors
+10%Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
5 checks passed
Real-user LCP: 1.3 s
1.3 sReal visitors wait 1.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user INP: 172 ms
172 msReal visitors wait 172 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user FCP: 1.3 s
1.3 sReal visitors see the first content after 1.3 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 391 ms
391 msReal visitors wait 391 ms for your server to start answering (75th percentile). Good is under 800 ms.
Total Blocking Time: 62 ms
62 msScripts block the page for only 62 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 3.5 MB in 245 requests
3.5 MBYour homepage downloads 3.5 MB in 245 requests on a phone: other files 1.3 MB (130), scripts 993 KiB (63) and images 607 KiB (33). Under 2 MB keeps phones on slow connections fast.
1 image below the first screen load straight away
1 image further down the page (38 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.
About 1.0 g of CO₂ per visit
1.00 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.00 g of CO₂e: 119.6 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
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (3 elements)
Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 3 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.
Main landmark should not be contained in another landmark (1 element)
Main 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 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.
Document should not have more than one main landmark (1 element)
Document should not have more than one main landmark: 1 element on the page fails this check, rated moderate by axe-core.
Alternative text of images should not be repeated as text (2 elements)
Alternative text of images should not be repeated as text: 2 elements on the page fail this check, rated minor by axe-core.
Elements with visible text labels do not have matching accessible names.
Elements with visible text labels do not have matching accessible names. (2 elements).
2 checks passed
Every image has alt text
All 28 images in the HTML carry an alt attribute.
44 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 44 passed and 6 failed. 2 mores need a person to judge. 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.
No social preview image
No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
1 link with vague text
1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
56 internal links, 8 external
The homepage links to 56 pages on optimera.se and 8 external pages.
6 checks passed
Meta description: 157 characters
Your meta description is 157 characters: “Optimera är byggvaruhuset för proffs. Handla bygg- och anläggningsmaterial från ledande varumärken i butik eller online…”.
One H1 headline
Your main headline reads: “Bygghandel för proffs”.
Title: 32 characters
Your title is a healthy 32 characters: “Optimera - Bygghandel för proffs”.
Canonical URL set
The canonical URL is https://www.optimera.se/.
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.optimera.se/sitemap_index.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.
No llms.txt
There is no https://www.optimera.se/llms.txt, a short Markdown guide to your key pages for AI tools (llmstxt.org). It is optional and few AI tools read it yet, so treat it as a cheap extra.
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.
Text is in the HTML
Your server sends the page's text in the HTML (328 words), so crawlers that don't run JavaScript still read it.
Other pages
4 pages share a title
/, https://www.optimera.se/hitta-butik, https://www.optimera.se/varumarken and https://www.optimera.se/varumarken/timbra all use the title “Optimera - Bygghandel för proffs”. Search engines can't tell which page to show for a search, so each competes with the others.
15 pages without a meta description
https://www.optimera.se/hitta-butik, https://www.optimera.se/kund-hos-oss/kontakt, https://www.optimera.se/mangda-och-dimensionera, https://www.optimera.se/specialistomraden, https://www.optimera.se/aktuellt and https://www.optimera.se/varumarken and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.
3 pages without an H1
https://www.optimera.se/aktuellt, https://www.optimera.se/varumarken and https://www.optimera.se/varumarken/timbra have no <h1> headline, so visitors and search engines get no clear main topic.
1 page with very little text
https://www.optimera.se/specialistomraden 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.
5 pages slow to respond
https://www.optimera.se/specialistomraden, https://www.optimera.se/aktuellt, https://www.optimera.se/varumarken, https://www.optimera.se/start/Villaeffekten and https://www.optimera.se/varumarken/timbra took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 42 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.
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
11 small tap targets
11 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
Missing source maps
Large scripts ship without source maps.
2 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
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.
Only about 202 words
The homepage has only about 202 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.
2 checks passed
2 short forms
2 short forms (1 field at most) are right on the homepage.
Analytics in place
Analytics detected: Google Tag Manager.
Privacy and tracking
1 tracker load before any consent
1Before a visitor clicks anything, the page loads Google Tag Manager (measured from a US location before any click). A consent tool (OneTrust) is installed; check it blocks these until visitors agree where the law requires it.
5 cookies set on arrival
5Opening the homepage sets 5 cookies (measured from a US location before any click).
9 other companies contacted
Loading the homepage contacts 9 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
Consent tool: OneTrust
A consent management tool (OneTrust) 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 optimera.se, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Nuxt
- Analytics
- Google Tag Manager
- Hosting
- Imperva
Company
- Founded
- 1996
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 36 issues on optimera.se, including 16 speed issues, 3 SEO issues and 5 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.