Website review, no card needed

olsen-olsen.com logo

olsen-olsen.com website review

Visit site (opens in a new tab)Reviewed 4 November 202638 issues · 80 checks

This review found 38 issues worth fixing on olsen-olsen.com, 13 of them high impact, across 80 checks. The most urgent: use efficient cache lifetimes. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.

  1. Homepage
  2. Phone render
  3. Links and pages
  4. Google PageSpeed

Google PageSpeed Insights (opens in a new tab), mobile

Full-page screenshot of olsen-olsen.com (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. olsen-olsen.com at 0.4 s0.4 s
  2. olsen-olsen.com at 0.9 s0.9 s
  3. olsen-olsen.com at 1.3 s1.3 s
  4. olsen-olsen.com at 1.8 s1.8 s
  5. olsen-olsen.com at 2.2 s2.2 s
  6. olsen-olsen.com at 2.7 s2.7 s
  7. olsen-olsen.com at 3.1 s3.1 s
  8. olsen-olsen.com at 3.5 s3.5 s

Speed

10 to fix63
  • Use efficient cache lifetimes

    1.1 s · 8.1 MB

    53 files are served with short cache lifetimes, so returning visitors download them again (8.1 MB).

  • Render-blocking requests

    2.8 s

    11 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.

  • Reduce unused JavaScript

    1.1 s · 818 KiB

    About 818 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.1 s faster on a phone.

  • Improve image delivery

    9.4 MB

    12 images could be 9.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

  • Mobile performance score: 63

    63/100

    Your mobile performance score is 63. Pages that score under 90 lose visitors before the first paint.

  • Font display

    900 ms

    Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 900 ms).

  • Reduce unused CSS

    600 ms · 86 KiB

    About 86 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.

  • 8 third-party services on the page

    8 third-party services load with your homepage (Yotpo, Shopify and weglot.com and others), adding 1.4 MB and 363 ms of main-thread time.

  • Shopify adds 114 ms

    114 ms

    Shopify costs a phone 114 ms of main-thread work and 1.1 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.

  • 1,742 HTML elements

    The page has 1,742 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

  • 6 long tasks on the main thread

    6 long tasks block the main thread while loading, the longest for 112 ms. During a long task the page ignores taps.

  • Legacy JavaScript

    70 KiB

    Polyfills for old browsers add 70 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.

  • Forced reflow

    Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 checks passed
  • Main-thread work: 1.8 s

    A phone's processor spends 1.8 s on main-thread work while loading, 619 ms of it running JavaScript. That is comfortably low.

  • Server response: 442 ms

    442 ms

    Your server sent the HTML in 442 ms, well inside Google's 600 ms guideline.

Core Web Vitals

5 to fix64
  • Largest Contentful Paint: 9.6 s

    9.6 s

    Your largest element takes 9.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “At Olsen+Olsen, we don't believe sustainable living should …”.

  • Time to Interactive: 40.3 s

    40.3 s

    The page becomes fully interactive after 40.3 s. Good is under 3.8 s.

  • First Contentful Paint: 3.3 s

    3.3 s

    The first text or image appears after 3.3 s on a phone. Good is under 1.8 s.

  • Speed Index: 5.2 s

    5.2 s

    Visually, the page fills in at 5.2 s (Speed Index). Good is under 3.4 s.

  • 19 images without width and height

    19 images have no width and height attributes, so the layout jumps as each one loads.

  • Not enough real-visitor data yet

    Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

2 checks passed
  • Cumulative Layout Shift: 0.068

    0.068

    The layout barely moves while loading (CLS 0.068, good is under 0.1).

  • Total Blocking Time: 128 ms

    128 ms

    Scripts block the page for only 128 ms while loading. Good is under 200 ms.

Images and page weight

5 to fix18
  • Page weight: 13.2 MB in 113 requests

    13.2 MB

    Your homepage downloads 13.2 MB in 113 requests on a phone: images 11.2 MB (32), other files 943 KiB (29) and scripts 751 KiB (33). Under 2 MB keeps phones on slow connections fast.

  • 4 images over 500 KB

    4 images weigh 9.5 MB together. On a phone connection a single image that size takes seconds.

  • 2 images far larger than shown

    1.6 MB

    2 images are downloaded at several times the size a phone draws them, for example CAR05523.jpg at 4,000 px wide, shown at 342 px. Resized copies would save about 1.6 MB.

  • 8 images in older formats

    8 images (10.2 MB) are JPEG, PNG or GIF. The same pictures as WebP or AVIF are usually much smaller at the same quality, and every current browser shows them.

  • 8 images below the first screen load straight away

    8 images further down the page (10.2 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

  • About 3.7 g of CO₂ per visit

    3.75 g

    By the Sustainable Web Design model, a visit to your homepage emits about 3.75 g of CO₂e: 449.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

Accessibility

7 to fixGoogle 8391
  • Links look like plain text

    1 link inside paragraphs relies on colour alone to stand out.

  • Scrollable region must have keyboard access (1 element)

    Scrollable region must have keyboard access: 1 element on the page fails this check, rated serious by axe-core.

  • 23 images without alt text

    23 images have no alt text, which hurts accessibility and image search.

  • All page content should be contained by landmarks (2 elements)

    All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.

  • Zoom is disabled

    The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

  • 12 form fields without a label

    12 form fields have no label, so screen readers announce an empty box and autofill guesses.

  • 1 link without text

    1 visible link has no text or label, so screen readers cannot say where it goes.

1 checks passed
  • 46 automated accessibility rules passed

    axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 52 WCAG 2.2 A/AA and best-practice rules on the phone render: 46 passed and 6 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.

SEO

4 to fixGoogle 6989
  • Invalid hreflang

    Your hreflang tags are invalid, so Google may show the wrong language version.

  • 1 link crawlers can't follow

    1 link has no real href, so search engines can't follow it.

  • 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.

  • One H1 headline

    Your <h1> is empty.

  • 34 internal links, 29 external

    The homepage links to 34 pages on olsen-olsen.com and 29 external pages.

7 checks passed
  • Meta description: 159 characters

    Your meta description is 159 characters: “Are you looking for a way to diminish your usage of plastic? Olsen + Olsen’s reusable eco-friendly products help keep y…”.

  • Title: 60 characters

    Your title is a healthy 60 characters: “Eco-Friendly Products | Sustainable Home Goods | Olsen+Olsen”.

  • Canonical URL set

    The canonical URL is https://www.olsen-olsen.com/.

  • Structured data in place

    Structured data found: BreadcrumbList.

  • 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.

  • XML sitemap found

    Your XML sitemap is reachable at https://www.olsen-olsen.com/sitemap.xml.

AI search readiness

1 to fix88
  • 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.olsen-olsen.com/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 (1,722 words), so crawlers that don't run JavaScript still read it.

Other pages

1 to fix95
  • 4 pages without a meta description

    https://www.olsen-olsen.com/pages/faq, https://www.olsen-olsen.com/collections/bamboo-toothbrushes, https://www.olsen-olsen.com/collections/all and https://www.olsen-olsen.com/blogs/news have no meta description, so Google writes the search snippet from whatever text it finds.

  • 6 pages slow to respond

    https://www.olsen-olsen.com/pages/company-history, https://www.olsen-olsen.com/pages/faq, https://www.olsen-olsen.com/pages/contact-us, https://www.olsen-olsen.com/eco-friendly-gift-ideas-for-families, https://www.olsen-olsen.com/collections/bamboo-toothbrushes and https://www.olsen-olsen.com/collections/all took over 3 s to send their HTML from our server.

  • 15 internal pages checked

    We fetched 15 pages linked from your homepage (of 17 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.

  • Titles are unique

    Every page we checked has its own title.

  • Every page has an H1

    Each page we checked has a main headline.

  • 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

2 to fixGoogle 9287
  • 5 small tap targets

    5 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

  • 6 low-resolution images

    6 images are served at too low a resolution for sharp phone screens.

  • Missing source maps

    Large scripts ship without source maps.

1 checks passed
  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

3 to fix67
  • 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.

  • A 10-field form

    Your longest form asks for 10 fields (5 required). Every extra field lowers completion.

  • 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 528 words of copy

    The homepage carries about 528 words of visible text.

3 checks passed
  • 8 calls to action

    The homepage has 8 calls to action, for example “Shop”, “Contact” and “Shop Now”.

  • Social proof on the page

    Social proof on the homepage: 65 testimonial or review blocks and a star rating.

  • Analytics in place

    Analytics detected: Cloudflare Web Analytics.

Privacy and tracking

  • 3 cookies set on arrival

    3

    Opening the homepage sets 3 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.

  • 13 other companies contacted

    Loading the homepage contacts 13 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 olsen-olsen.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 6 apps. Each one is code from another company running for your shoppers.

Apps your storefront loads

Inbox · yotpo.com · cloudfront.net · nfcube.com · chimpstatic.com · weglot.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
jQuery
E-commerce
Shopify
Hosting
Cloudflare

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 olsen-olsen.com, including 15 speed issues, 4 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

By continuing you agree to the Terms and acknowledge the Privacy Policy.

Free requests are written in the order they come in, so it can take a while. Pay $25 and yours is ready within a few hours. Either way you get a shareable link and a PDF.

  • No subscription
  • Free, or $25 to skip the line
  • Money-back guarantee

14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.

Get the full playbook · $25