Website review, no card needed

filterfinder.dk logo

filterfinder.dk website review

Visit site (opens in a new tab)Reviewed 5 November 202638 issues · 85 checks

This review found 38 issues worth fixing on filterfinder.dk, 13 of them high impact, across 85 checks. The most urgent: page weight: 4.8 MB in 456 requests. 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

Real-visitor load time (LCP)75th percentile, phones
4.3 s3.5 sMay 23Jun 274.2 s
Show as table
DateReal-visitor load time (LCP)
May 23, 20263.6 s
May 30, 20264.0 s
Jun 6, 20264.0 s
Jun 13, 20264.0 s
Jun 20, 20264.0 s
Jun 27, 20264.2 s

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

Full-page screenshot of filterfinder.dk (phone) rendered by Google PageSpeed Insights

How it loaded on a phone

  1. filterfinder.dk at 0.5 s0.5 s
  2. filterfinder.dk at 1.0 s1.0 s
  3. filterfinder.dk at 1.4 s1.4 s
  4. filterfinder.dk at 1.9 s1.9 s
  5. filterfinder.dk at 2.4 s2.4 s
  6. filterfinder.dk at 2.9 s2.9 s
  7. filterfinder.dk at 3.4 s3.4 s
  8. filterfinder.dk at 3.9 s3.9 s

Speed

9 to fix55
  • Main-thread work: 4.9 s

    A phone's processor spends 4.9 s on main-thread work while loading, 3.1 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 (Google Tag Manager, ZenDesk and Shopify and others), adding 2.3 MB and 1.2 s of main-thread time.

  • Reduce unused JavaScript

    450 ms · 852 KiB

    About 852 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

  • Mobile performance score: 55

    55/100

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

  • Render-blocking requests

    750 ms

    4 files block the first paint until they finish downloading. Deferring or inlining them could save about 750 ms.

  • Google Tag Manager adds 341 ms

    341 ms

    Google Tag Manager costs a phone 341 ms of main-thread work and 351 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 CSS

    300 ms · 54 KiB

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

  • ZenDesk adds 297 ms

    297 ms

    ZenDesk costs a phone 297 ms of main-thread work and 478 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 213 ms

    213 ms

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

  • Improve image delivery

    100 ms · 104 KiB

    12 images could be 104 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 100 ms faster on a phone.

  • 12 long tasks on the main thread

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

  • Legacy JavaScript

    100 ms · 47 KiB

    Polyfills for old browsers add 47 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 100 ms faster on a phone.

  • Font display

    100 ms

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

  • Use efficient cache lifetimes

    50 ms · 49 KiB

    16 files are served with short cache lifetimes, so returning visitors download them again (49 KiB).

  • Minify JavaScript

    15 KiB

    15 KiB could be saved by minifying JavaScript.

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

1 checks passed
  • Server response: 100 ms

    100 ms

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

Core Web Vitals

6 to fix53
  • Time to Interactive: 24.2 s

    24.2 s

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

  • Largest Contentful Paint: 7.4 s

    7.4 s

    Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Get Started & Find Your Filters With 1,000,000+ cross refer…”.

  • Speed Index: 7.1 s

    7.1 s

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

  • Total Blocking Time: 438 ms

    438 ms

    Scripts block taps and scrolling for 438 ms in total while the page loads. Good is under 200 ms.

  • 18 images without width and height

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

  • First Contentful Paint: 1.8 s

    1.8 s

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

  • Largest content (LCP) held steady for real visitors

    +8%

    Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' largest content (lcp) went from 3.6 s to 4.2 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

1 checks passed
  • Cumulative Layout Shift: 0.1

    0.1

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

Images and page weight

1 to fix70
  • Page weight: 4.8 MB in 456 requests

    4.8 MB

    Your homepage downloads 4.8 MB in 456 requests on a phone: scripts 1.9 MB (111), other files 1.6 MB (267) and images 733 KiB (51). Under 2 MB keeps phones on slow connections fast.

  • 1 image below the first screen load straight away

    1 image further down the page (62 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

  • About 1.4 g of CO₂ per visit

    1.36 g

    By the Sustainable Web Design model, a visit to your homepage emits about 1.36 g of CO₂e: 162.8 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

8 to fixGoogle 8290
  • 1 button without a name

    1 button has no accessible name, so screen readers announce just “button”.

  • 2 text elements with low contrast

    2 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.

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

  • 2 images without alt text

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

  • Landmarks should have a unique role or role/label/title (i.e. accessible name) combination (1 element)

    Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

  • 2 form fields without a label

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

  • Headings skip levels

    Headings skip levels (h1 → h3, h1 → h3 and h2 → h5), which makes the page harder to scan with a screen reader.

1 checks passed
  • 50 automated accessibility rules passed

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

SEO

3 to fixGoogle 9284
  • Title is short (12 characters)

    Your title is only 12 characters: “FilterFinder”. Between 30 and 65 characters leaves room to say what you do and for whom.

  • 2 H1 headlines

    There are 2 <h1> headlines (“Get Started & Find Your Filters” and “Innovating Filtration Since 1968”). One clear main headline is easier for people and search engines.

  • Structured data has 1 problem

    Structured data found (BreadcrumbList, CollectionPage, ImageObject and Organization) but with 1 problem, for example “Organization: url points at a different host (https://www.filterfinderonline.com)”.

  • 18 internal links, 70 external

    The homepage links to 18 pages on filterfinder.dk and 70 external pages.

5 checks passed
  • Meta description: 112 characters

    Your meta description is 112 characters: “Discover more than 600,000 part numbers quickly, and easily by searching our huge range of products and filters.”.

  • Canonical URL set

    The canonical URL is https://www.filterfinder.dk/.

  • 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.filterfinder.dk/sitemap.xml.

AI search readiness

100
  • Opted out of AI training for 5 crawlers

    robots.txt blocks GPTBot, ClaudeBot, Google-Extended, Applebot-Extended and CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

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 (893 words), so crawlers that don't run JavaScript still read it.

  • llms.txt published

    The site publishes https://www.filterfinder.dk/llms.txt (6 KiB, 8 links), a plain-text guide to the site for AI tools.

Other pages

3 to fix65
  • 1 linked page is broken

    Your homepage links to https://www.filterfinder.dk/apps/advanced-wishlist, which answers with an error. Visitors hit a dead end and search engines drop it.

  • 4 pages without a meta description

    https://www.filterfinder.dk/blogs/news, https://www.filterfinder.dk/policies/terms-of-service, https://www.filterfinder.dk/policies/privacy-policy and https://www.filterfinder.dk/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

  • 10 pages without an H1

    https://www.filterfinder.dk/pages/contact, https://www.filterfinder.dk/pages/fleetguard, https://www.filterfinder.dk/pages/pall, https://www.filterfinder.dk/pages/hydac, https://www.filterfinder.dk/pages/donaldson and https://www.filterfinder.dk/pages/our-story and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.

  • 10 pages with very little text

    https://www.filterfinder.dk/pages/contact, https://www.filterfinder.dk/pages/fleetguard, https://www.filterfinder.dk/pages/pall, https://www.filterfinder.dk/pages/hydac, https://www.filterfinder.dk/pages/donaldson and https://www.filterfinder.dk/pages/our-story and 4 others have 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.

  • 12 internal pages checked

    We fetched 12 pages linked from your homepage and read each the way a search engine does.

4 checks passed
  • 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.

  • No linked page is hidden from search

    None of the pages we checked carries a noindex tag.

  • Every page has a title

    All 10 pages that loaded have a <title>.

Best practices

3 to fixGoogle 7776
  • 3 broken images

    3 images failed to load on a phone, for example https://www.filterfinder.dk/.

  • Deprecated browser APIs

    The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

  • 6 JavaScript errors while loading

    6 errors were logged to the browser console while the page loaded, for example “Unexpected token '<'”.

2 checks passed
  • Tap targets are thumb-sized

    24 of 24 tappable elements near the top are at least 24 px.

  • Mobile viewport set

    The page declares a mobile viewport.

Content and conversion

5 to fix56
  • 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 social proof

    No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

  • Local business without LocalBusiness data

    Your homepage shows a street address but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

  • No phone number on the homepage

    A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

  • 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 opening hours

    The homepage shows no opening hours. If customers visit or call, show when.

  • No map or directions link

    There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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

    The homepage carries about 498 words of visible text.

3 checks passed
  • 6 calls to action

    The homepage has 6 calls to action, for example “Türkiye ₺ TRY”, “Contact” and “Learn More →”.

  • 7 short forms

    7 short forms (1 field at most) are right on the homepage.

  • Analytics in place

    Analytics detected: Google Tag Manager, Google Analytics, Microsoft Clarity and Hotjar.

Privacy and tracking

  • 6 trackers load before any consent

    6

    Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, Klaviyo and Microsoft Ads and 1 more (measured from a US location before any click). A consent tool (CookieYes) is installed; check it blocks these until visitors agree where the law requires it.

  • 17 cookies set on arrival

    17

    Opening the homepage sets 17 cookies (measured from a US location before any click).

  • 42 other companies contacted

    Loading the homepage contacts 42 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.

1 checks passed
  • Consent tool: CookieYes

    A consent management tool (CookieYes) 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 filterfinder.dk, 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

Tagfly Tag Manager · Powerful Form Builder · Klaviyo Email Marketing Sms · O Request A Quote · Yoast Seo · Page Speed Optimizer · Share Cart App · Wholesale All In One · Freegifts · w3apps.co · synctrack.io · bogos.io · kxcdn.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
Analytics
Google Analytics | Google Tag Manager | Hotjar | Microsoft Clarity
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 filterfinder.dk, including 15 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

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