feenstra.com website review

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

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

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

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

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

1 file blocks the first paint until they finish downloading. Deferring or inlining it could save about 450 ms.

About 100 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.

A phone's processor spends 3.9 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.

7 third-party services load with your homepage (cookiebot.eu, Mopinion and XiTi and others), adding 285 KiB and 326 ms of main-thread time.

2 images could be 34 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

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

3 KiB could be saved by minifying CSS.

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

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “homepage header 7”.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 114 ms to 117 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

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

ARIA dialog and alertdialog nodes should have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

All page content should be contained by landmarks: 4 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 on the page fails this check, rated moderate by axe-core.

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

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

Structured data found (Organization) but with 2 problems, for example “Organization: logo is not an absolute URL ("/_resources/themes/default/images/logo.png?m=1793704095…”.

No XML sitemap at https://www.feenstra.com/sitemap.xml, so Google discovers your pages only by following links.

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

The homepage links to 110 pages on feenstra.com and 9 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no /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.

We fetched 15 pages linked from your homepage (of 47 found) and read each the way a search engine does.

Large scripts ship without source maps.

No Strict-Transport-Security header, so browsers may still try plain http first on a return visit.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

No Referrer-Policy header, so full URLs can leak to the sites you link to.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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.

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

Social proof on the homepage: a star rating. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

The homepage carries about 512 words of visible text.

DMARC is set to p=none, so mail pretending to be feenstra.com is still delivered. Reports are on, so moving to quarantine is the next step.

Your SPF record doesn't end in -all or ~all, so it doesn't stop other servers sending as you: “v=spf1 redirect=4412yljs._spf._d.mim.ec”.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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

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

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