norpac.com website review

22 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

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

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

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

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

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

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

1 third-party service load with your homepage (Adobe TypeKit), adding 130 KiB and 0 ms of main-thread time.

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.

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.

Real visitors wait 1.9 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 10.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “tom-fessler-tractor”.

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

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

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

Real visitors wait 3.6 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors see the first content after 2.9 s (75th percentile). Good is under 1.8 s.

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

Your homepage downloads 2.6 MB in 102 requests on a phone: images 1.9 MB (33), scripts 369 KiB (26) and fonts 128 KiB (3). Under 2 MB keeps phones on slow connections fast.

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

tom-fessler-tractor-1024x573.webp 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).

1 image (93 KiB) is 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.

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

22 tap targets are too small or too close together to hit reliably with a finger.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

28 visible links have no text or label, so screen readers cannot say where they go.

No meta description, so Google writes its own snippet from whatever text it finds.

There is no <h1>, so neither visitors nor Google get a clear main headline.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

5 links have no real href, so search engines can't follow them.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 45 pages on norpac.com and 0 external pages.

A phone browser shows 1,422 words, but the HTML your server sends has only 338. GPTBot, ClaudeBot and PerplexityBot read that HTML without running JavaScript, so they see an almost empty page. Server-side rendering or pre-rendering fixes it.

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.

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

https://norpac.com/retail-products, https://norpac.com/product-category/jamba-at-home-smoothies, https://norpac.com/product-category/vegetable-blends, https://norpac.com/product-category/vegetable-classics, https://norpac.com/product-category/roasted-vegetables and https://norpac.com/product-category/grande-classics-gourmet-vegetable-blends and 7 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://norpac.com/retail-products, https://norpac.com/product-category/jamba-at-home-smoothies, https://norpac.com/product-category/vegetable-blends, https://norpac.com/product-category/vegetable-classics, https://norpac.com/product-category/roasted-vegetables and https://norpac.com/product-category/grande-classics-gourmet-vegetable-blends and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://norpac.com/retail-products, https://norpac.com/product-category/jamba-at-home-smoothies, https://norpac.com/product-category/vegetable-blends, https://norpac.com/product-category/vegetable-classics, https://norpac.com/product-category/roasted-vegetables and https://norpac.com/product-category/grande-classics-gourmet-vegetable-blends and 7 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.

https://norpac.com/product-category/jamba-at-home-smoothies, https://norpac.com/product-category/roasted-vegetables, https://norpac.com/product-category/premium-vegetables, https://norpac.com/product-category/steam-of-the-crop, https://norpac.com/product-category/fruits and https://norpac.com/product-category/soup-sensations took over 3 s to send their HTML from our server.

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

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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.

There is no form on the homepage, so every lead has to click through to another page first.

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 1,422 words of visible text.

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

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.

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