controlled-cs.com website review

7 images could be 5.2 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 350 ms faster on a phone.

5 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and cleanroomcleaning.com and others), adding 6.1 MB and 560 ms of main-thread time.

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

7 files block the first paint until they finish downloading. Deferring or inlining them could save about 900 ms.

About 653 KiB of JavaScript is downloaded but never used on this page.

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

cleanroomcleaning.com costs a phone 49 ms of main-thread work and 4.8 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.

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

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

6 KiB could be saved by minifying JavaScript.

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

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

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

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

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

Chrome's UX Report (opens in a new tab) has too little real-visitor traffic for this site, so the figures here are lab measurements from Google's test phone on a throttled 4G connection.

Your homepage downloads 8.7 MB in 50 requests on a phone: images 5.5 MB (15), fonts 1.5 MB (7) and scripts 1.2 MB (14). Under 2 MB keeps phones on slow connections fast.

3 images weigh 5.3 MB together. On a phone connection a single image that size takes seconds.

2 images are downloaded at several times the size a phone draws them, for example Screenshot-2025-04-24-120614.png at 1,746 px wide, shown at 347 px. Resized copies would save about 2.7 MB.

6 images (5.5 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.

1 image further down the page (3.4 MB) 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 2.47 g of CO₂e: 296.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

Your meta description is 180 characters; Google truncates after about 160, so the end of your pitch is cut.

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

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

The homepage links to 58 pages on controlled-cs.com and 2 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.

/contact-us, /industries, /life-sciences and /advanced-manufacturing have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

4 resources load over plain http on your https page (for example http://controlled-cs.com/wp-content/uploads/2026/02/partnerships-2-1.webp); browsers block or warn about them.

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.

1 link go through two or more redirects, for example http://controlled-cs.com/contact-us.

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.

controlled-cs.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.

controlled-cs.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.

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

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 analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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

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.

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