companycam.com website review

Unpkg costs a phone 11.2 s of main-thread work and 88 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

About 724 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

Google Tag Manager costs a phone 1.6 s of main-thread work and 1.0 MB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

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

8 third-party services load with your homepage (Unpkg, Google Tag Manager and Optanon and others), adding 2.3 MB and 13.9 s of main-thread time.

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

About 279 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 980 ms faster on a phone.

16 images could be 999 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

Optanon costs a phone 615 ms of main-thread work and 258 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.

intellimize.co costs a phone 193 ms of main-thread work and 740 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.

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 100 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.

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

Your largest element takes 18.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “two men working on a roofing project”.

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

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

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

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

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

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

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

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

Your homepage downloads 18.4 MB in 230 requests on a phone: media 10.4 MB (2), other files 3.3 MB (57) and scripts 2.4 MB (41). Under 2 MB keeps phones on slow connections fast.

image-blurb.png weighs 539 KiB. On a phone connection a single image that size takes seconds.

6 images (975 KiB) 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.

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

5 images are downloaded at several times the size a phone draws them, for example image-blurb.png at 605 px wide, shown at 191 px. Resized copies would save about 445 KiB.

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

4 buttons have no accessible name, so screen readers announce just “button”.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

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

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

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

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

Structured data found (BreadcrumbList, Person, WebPage and WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("https://companycam.com/Company Cam SEO")”.

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

The homepage links to 247 pages on companycam.com and 37 external pages.

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

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

2 images failed to load on a phone, for example https://companycam.imgix.net/images/homepage-2025/Mask-group-1.png.

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

5 errors were logged to the browser console while the page loaded, for example “Refused to apply style from 'https://companycam.com/typi/typi' because its MIME type ('text/html') is not a supported s…”.

The page has no <!DOCTYPE html>, so browsers render it in quirks mode.

5 images are served at too low a resolution for sharp phone screens.

HSTS is set, but max-age is 30 days; one year is the recommended minimum.

1 link go through two or more redirects, for example https://instagram.com/companycam.

No Permissions-Policy header to switch off camera, microphone and location for embedded content.

X-XSS-Protection is set to “1; mode=block”; the header is deprecated and can introduce bugs. Use 0 or remove it.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Your longest form asks for 10 fields (0 required). Every extra field lowers completion.

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.

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

Before a visitor clicks anything, the page loads Amplitude, Google Ads, Google Analytics, Google Tag Manager and LinkedIn Insight and 6 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.

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

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