Website review, no card needed
anderson-negele.com website review
Visit site (opens in a new tab)Reviewed 21 October 202640 issues · 90 checks
This review found 40 issues worth fixing on anderson-negele.com, 14 of them high impact, across 90 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
68D- #110,909 of 126,522 reviewed websitesbeats 10%
- #65,687 of 70,503 online storesbeats 5%
- #791 of 925 BigCommerce storesbeats 11%
Closest competitors among BigCommerce stores
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 2.8 s |
| May 9, 2026 | 2.8 s |
| May 16, 2026 | 2.8 s |
| May 23, 2026 | 2.8 s |
| May 30, 2026 | 2.7 s |
| Jun 6, 2026 | 2.7 s |
| Jun 13, 2026 | 2.7 s |
| Jun 20, 2026 | 2.8 s |
| Jun 27, 2026 | 2.8 s |
| Jul 4, 2026 | 2.8 s |
| Jul 11, 2026 | 2.8 s |
| Jul 18, 2026 | 2.9 s |
| Jul 25, 2026 | 2.8 s |
| Aug 1, 2026 | 2.9 s |
| Aug 8, 2026 | 2.8 s |
| Aug 15, 2026 | 2.8 s |
| Aug 22, 2026 | 2.7 s |
| Aug 29, 2026 | 2.7 s |
| Sep 5, 2026 | 2.8 s |
| Sep 12, 2026 | 2.8 s |
| Sep 19, 2026 | 2.9 s |
| Sep 26, 2026 | 2.9 s |
| Oct 3, 2026 | 2.9 s |
| Oct 10, 2026 | 2.9 s |
| Oct 17, 2026 | 2.9 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 135 ms |
| May 9, 2026 | 132 ms |
| May 16, 2026 | 135 ms |
| May 23, 2026 | 137 ms |
| May 30, 2026 | 140 ms |
| Jun 6, 2026 | 145 ms |
| Jun 13, 2026 | 136 ms |
| Jun 20, 2026 | 132 ms |
| Jun 27, 2026 | 122 ms |
| Jul 4, 2026 | 127 ms |
| Jul 11, 2026 | 126 ms |
| Jul 18, 2026 | 123 ms |
| Jul 25, 2026 | 120 ms |
| Aug 1, 2026 | 113 ms |
| Aug 8, 2026 | 116 ms |
| Aug 15, 2026 | 125 ms |
| Aug 22, 2026 | 128 ms |
| Aug 29, 2026 | 136 ms |
| Sep 5, 2026 | 138 ms |
| Sep 12, 2026 | 148 ms |
| Sep 19, 2026 | 149 ms |
| Sep 26, 2026 | 138 ms |
| Oct 3, 2026 | 137 ms |
| Oct 10, 2026 | 119 ms |
| Oct 17, 2026 | 122 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
1.1 s
2.3 s
3.4 s
4.5 s
5.6 s
6.8 s
7.9 s
9.0 s
Speed
Render-blocking requests
2.3 s12 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Main-thread work: 10.2 s
A phone's processor spends 10.2 s on main-thread work while loading, 6.3 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Mobile performance score: 33
33/100Your mobile performance score is 33 (desktop: 68). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
8 third-party services on the page
8 third-party services load with your homepage (Google Tag Manager, Hubspot and FullStory and others), adding 1.4 MB and 2.0 s of main-thread time.
Reduce unused JavaScript
600 ms · 1,013 KiBAbout 1,013 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.
Improve image delivery
1.4 MB6 images could be 1.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Google Tag Manager adds 816 ms
816 msGoogle Tag Manager costs a phone 816 ms of main-thread work and 507 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.
20 long tasks on the main thread
20 long tasks block the main thread while loading, the longest for 538 ms. During a long task the page ignores taps.
Use efficient cache lifetimes
468 KiB22 files are served with short cache lifetimes, so returning visitors download them again (468 KiB).
Reduce unused CSS
300 ms · 90 KiBAbout 90 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.
Hubspot adds 286 ms
286 msHubspot costs a phone 286 ms of main-thread work and 111 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.
Font display
50 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 50 ms).
Legacy JavaScript
33 KiBPolyfills for old browsers add 33 KiB JavaScript that modern phones do not need.
Phones get a much slower page than desktops
Desktop scores 68 but mobile only 33. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
1 checks passed
Server response: 45 ms
45 msYour server sent the HTML in 45 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.
Time to Interactive: 26.8 s
26.8 sThe page becomes fully interactive after 26.8 s. Good is under 3.8 s.
Speed Index: 13.0 s
13.0 sVisually, the page fills in at 13.0 s (Speed Index). Good is under 3.4 s.
Total Blocking Time: 2.8 s
2.8 sScripts block taps and scrolling for 2.8 s in total while the page loads. Good is under 200 ms.
Largest Contentful Paint: 5.9 s
5.9 sYour largest element takes 5.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Slide image”.
First Contentful Paint: 3.4 s
3.4 sThe first text or image appears after 3.4 s on a phone. Good is under 1.8 s.
Real-user LCP: 2.9 s
2.9 sReal visitors wait 2.9 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user CLS: 0.18
0.18For real visitors the layout shifts by 0.18 (75th percentile). Good is under 0.1.
Real-user FCP: 2.4 s
2.4 sReal visitors see the first content after 2.4 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 899 ms
899 msReal visitors wait 899 ms for your server to start answering (75th percentile). Good is under 800 ms.
Largest content (LCP) held steady for real visitors
+5%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 2.8 s to 2.9 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 122 ms
122 msReal visitors wait 122 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Tap response (INP) got 10% faster for real visitors
-10%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 135 ms to 122 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Cumulative Layout Shift: 0
0The layout barely moves while loading (CLS 0, good is under 0.1).
Images and page weight
Page weight: 5.2 MB in 247 requests
5.2 MBYour homepage downloads 5.2 MB in 247 requests on a phone: scripts 2.6 MB (97), images 2.2 MB (40) and fonts 166 KiB (4). Under 2 MB keeps phones on slow connections fast.
An image on the first screen is lazy-loaded
image 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).
About 1.5 g of CO₂ per visit
1.48 gBy the Sustainable Web Design model, a visit to your homepage emits about 1.48 g of CO₂e: 178.1 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
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
<html> element must have a lang attribute (1 element)
<html> element must have a lang attribute: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (4 elements)
All page content should be contained by landmarks: 4 elements on the page fail this check, rated moderate by axe-core.
Heading levels should only increase by one (1 element)
Heading levels should only increase by one: 1 element on the page fails 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.
No page language
The <html> element has no lang attribute, so screen readers may read the page in the wrong voice and accent.
2 checks passed
Every image has alt text
All 12 images in the HTML carry an alt attribute.
47 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: 47 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (94 characters)
Your title is 94 characters, so Google will cut it off around 60: “Anderson-Negele | Manufacturer of Hygienic Sensors & Process Instrumentation | Anderson-N…”.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
9 H1 headlines
There are 9 <h1> headlines (“ILM-4 Conductivity measurement that's ready when …”, “Turn your Process Chain into your Value Chain” and “It won’t get more hygienic: contactless temperatu…”). One clear main headline is easier for people and search engines.
No social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
No X (Twitter) card tag
No twitter:card tag. X falls back to Open Graph, which is incomplete here.
22 internal links, 6 external
The homepage links to 22 pages on anderson-negele.com and 6 external pages.
4 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Anderson-Negele develops & produces a wide range of sanitary sensors and hygienic solutions for process control in Food…”.
Canonical URL set
The canonical URL is https://www.anderson-negele.com/.
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.anderson-negele.com/sitemap.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.
Some text only appears after JavaScript runs
41%The HTML your server sends has 254 of the 622 words a browser shows. AI crawlers don't run JavaScript, so they miss the rest.
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.
llms.txt published
The site publishes https://www.anderson-negele.com/llms.txt (15 KiB, 58 links), a plain-text guide to the site for AI tools.
Other pages
4 pages with very little text
https://www.anderson-negele.com/knowledge-and-resources, https://www.anderson-negele.com/products, https://www.anderson-negele.com/contact-sales and https://www.anderson-negele.com/terms-conditions 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.
7 checks passed
Linked pages load
All 12 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 12 pages that loaded have a meta description.
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 12 pages that loaded have a <title>.
Best practices
1 third-party cookie
1 third-party cookie is set on load; browsers are restricting these, so whatever relies on them breaks.
1 distorted image
1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.
Missing source maps
Large scripts ship without source maps.
Browser-reported issues
Chrome logged issues while loading the page (“Cookie”).
3 checks passed
No console errors
No JavaScript errors were logged while the page loaded on a phone.
Tap targets are thumb-sized
32 of 37 tappable elements near the top are at least 24 px.
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 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 opening hours
The homepage shows no opening hours. If customers visit or call, show when.
No form on the homepage
There is no form on the homepage, so every lead has to click through to another page first.
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 622 words of copy
The homepage carries about 622 words of visible text.
4 checks passed
2 calls to action
The homepage has 2 calls to action, for example “Contact Us” and “Contact Sales”.
Analytics in place
Analytics detected: Google Tag Manager.
Direct contact links
Visitors can reach you directly: 1 phone link and 1 email link.
Phone number on the homepage
Your phone number is on the homepage as a tap-to-call link.
Privacy and tracking
8 trackers load before any consent
8Before a visitor clicks anything, the page loads FullStory, Google Ads, Google Analytics, Google Tag Manager and HubSpot and 3 mores (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.
20 cookies set on arrival
20Opening the homepage sets 20 cookies (measured from a US location before any click).
41 other companies contacted
Loading the homepage contacts 41 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 anderson-negele.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- HubSpot CMS
- Framework
- Next.js
- E-commerce
- BigCommerce;BigCommerce Catalyst
- Analytics
- Google Tag Manager
- Hosting
- Vercel
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on anderson-negele.com, including 21 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
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.