customertimes.com website review

About 2.0 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.7 s faster on a phone.

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

38 files are served with short cache lifetimes, so returning visitors download them again (550 KiB).

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

Google Tag Manager costs a phone 1.1 s of main-thread work and 631 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.

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

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

8 third-party services load with your homepage (Google Tag Manager, website-files.com and Google CDN and others), adding 13.9 MB and 4.6 s of main-thread time.

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

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

website-files.com costs a phone 689 ms of main-thread work and 652 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.

hsappstatic.net costs a phone 585 ms of main-thread work and 711 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.

Hubspot costs a phone 580 ms of main-thread work and 379 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 478 ms. During a long task the page ignores taps.

37 KiB JavaScript is shipped twice across bundles. Google estimates it would make the page about 300 ms faster on a phone.

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

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

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 14.7 MB in 200 requests on a phone: other files 9.3 MB (77), scripts 4.3 MB (59) and images 451 KiB (40). Under 2 MB keeps phones on slow connections fast.

6a15c3022ae6e74428fe394d_d542fd456be687ca419adbf83e6870e4_gr 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).

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

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

ARIA attributes must conform to valid names: 1 element on the page fails this check, rated critical by axe-core.

3 frames have no title, so screen-reader users cannot tell what they contain.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Banner landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

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

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

The homepage links to 139 pages on customertimes.com and 5 external pages.

/industries/software took over 3 s to send its HTML from our server.

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

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

The page uses 1 deprecated browser API that will stop working in future browsers (“Unload event listeners are deprecated and will be removed.”).

3 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_CONNECTION_RESET”.

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

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

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.

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

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

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

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 2,328 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 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 9 cookies, 2 of them by other companies (measured from a US location before any click).

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