geospace.com website review

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

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

About 1.8 MB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 9.4 s faster on a phone.

Your mobile performance score is 9. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

About 2.5 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.

8 third-party services load with your homepage (Google CDN, YouTube and Google Tag Manager and others), adding 3.0 MB and 2.7 s of main-thread time.

Google CDN costs a phone 942 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.

YouTube costs a phone 737 ms of main-thread work and 991 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.

Google Tag Manager costs a phone 513 ms of main-thread work and 325 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 block the main thread while loading, the longest for 443 ms. During a long task the page ignores taps.

Hubspot costs a phone 322 ms of main-thread work and 307 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.

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

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

28 KiB could be saved by minifying CSS.

170 KiB could be saved by minifying JavaScript.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

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

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 6.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

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

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

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

Your largest element takes 18.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “OUR BUSINESS SEGMENT Smart Water Our smart water products d…”.

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

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

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

The layout shifts by 0.373 while loading, so content jumps under the reader's thumb. Good is under 0.1.

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

Over the last 25 four-week periods to 2026-10-31, real Chrome visitors' tap response (inp) went from 115 ms to 131 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 5.5 s to 6.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 8.6 MB in 187 requests on a phone: scripts 4.6 MB (65), stylesheets 2.1 MB (37) and images 600 KiB (44). Under 2 MB keeps phones on slow connections fast.

3 images further down the page (121 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

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

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

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

All page content should be contained by landmarks: 22 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.

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

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

3 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

The homepage links to 122 pages on geospace.com and 11 external pages.

/company/investor-relations, /contact/distributor, /company/hse, /company/customer-and-supplier-relations, /company/quality and /solutions/smart-water-management-solutions/asset-protection have no meta description, so Google writes the search snippet from whatever text it finds.

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://fonts.googleapis.com/css?family=%7CSource+Sans+Pro%3A%2C+%2C+%2C+%2C+%2C+%2C+%2C+%…”.

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

1 image is served at too low a resolution for sharp phone screens.

Chrome logged issues while loading the page (“Cookie”).

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

No Content-Security-Policy header, the main browser-side defence against injected scripts.

Neither X-Frame-Options nor a CSP frame-ancestors policy is set, so any site can embed yours in a frame.

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

4 links go through two or more redirects, for example https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fwww.geospace.com%2Fevents%2F4d-forum-insight-into-action%2F.

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.

geospace.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

geospace.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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

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 341 words of visible text.

geospace.com has no SPF record, so mail servers can't tell which servers may send email as you. Your mail lands in spam more often, and anyone can send mail pretending to be you.

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, Google Analytics, Google Tag Manager, HubSpot and Microsoft Clarity (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 17 cookies, 1 of them by other companies (measured from a US location before any click).

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