csdsinc.com website review

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

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

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

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

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

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

About 1.3 MB of JavaScript is downloaded but never used on this page.

20 long tasks block the main thread while loading, the longest for 1.1 s. During a long task the page ignores taps.

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

Google Tag Manager costs a phone 340 ms of main-thread work and 374 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.

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

About 26 KiB of CSS is downloaded but never applied on this page.

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.

4 KiB could be saved by minifying CSS.

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 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 38.6 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

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

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

Real visitors wait 232 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

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

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

8 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-17, real Chrome visitors' tap response (inp) went from 248 ms to 242 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 30.7 MB in 118 requests on a phone: images 27.3 MB (54), scripts 2.5 MB (17) and other files 390 KiB (33). Under 2 MB keeps phones on slow connections fast.

7 images weigh 4.3 MB together. On a phone connection a single image that size takes seconds.

16 images (6.0 MB) are 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.

wingtra-survey-61-logo.png 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 further down the page (35 KiB) download before anyone scrolls to it. Adding loading="lazy" lets the first screen load first.

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

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

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

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

2 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

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

Your title is only 11 characters: “CSDS | Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 8 <h1> headlines (“Trimble ST30 Smart Target”, “Blue UAS Cleared” and “Seamless data sync from the field to ArcGIS® Fiel…”). One clear main headline is easier for people and search engines.

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

Structured data found (Organization and WebSite) but with 3 problems, for example “WebSite: missing name”.

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

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

The homepage links to 503 pages on csdsinc.com and 8 external pages.

Your Organization JSON-LD is missing name, url, logo, sameAs (social profiles) 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.

/other-questions/terms-conditions, /LocationFinder and /contact-us have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 10 pages by a URL that isn't their canonical one, for example /LocationFinder, whose canonical is /locationfinder. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

/other-questions/terms-conditions has no <h1> headline, so visitors and search engines get no clear main topic.

/catalog/solutions-products/surveying-mapping-solutions/gnss-robotic-total-stations/gnss-receivers-antennas, /catalog/solutions-products/surveying-mapping-solutions/gnss-robotic-total-stations/robotic-total-stations, /catalog/solutions-products/surveying-mapping-solutions/gnss-robotic-total-stations/360-prisms, /catalog/solutions-products/surveying-mapping-solutions/gnss-robotic-total-stations/radios-antennas, /catalog/solutions-products/surveying-mapping-solutions/gnss-robotic-total-stations/chargers-batteries-and-battery-packs and /catalog/solutions-products/surveying-mapping-solutions/data-collectors and 2 others took over 3 s to send their HTML from our server.

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

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 404 ()”.

Large scripts ship without source maps.

http://csdsinc.com does not redirect to https, so some visitors land on the insecure version.

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

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.

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

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

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.

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.

The homepage carries about 1,446 words of visible text.

The page uses urgency cues (a countdown or limited-time wording).

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 and Google Tag Manager (measured from a US location before any click). No consent tool was detected. Visitors from the EU, UK and several US states must be asked first.

Opening the homepage sets 12 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 19 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.