commcentric.com website review

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

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

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

8 third-party services load with your homepage (Squarespace, Google Tag Manager and azure.com and others), adding 5.1 MB and 944 ms of main-thread time.

About 131 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.

1 file is served with short cache lifetimes, so returning visitors download them again (61 KiB).

Squarespace costs a phone 640 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.

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

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

squarespace-cdn.com costs a phone 0 ms of main-thread work and 3.4 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.

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

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

sqspcdn.com costs a phone 75 ms of main-thread work and 322 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.

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.

Your largest element takes 20.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “About Us_Header Background.png”.

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

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

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

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

1 image 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 5.1 MB in 111 requests on a phone: images 3.4 MB (43), scripts 1.5 MB (46) and stylesheets 164 KiB (9). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example About+Us_Header+Background.png at 2,500 px wide, shown at 390 px. Resized copies would save about 434 KiB.

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

Links must have discernible text: 4 elements on the page fail this check, rated serious by axe-core.

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

Headings skip levels (h2 → h4, h2 → h4 and h2 → 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.

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

Your canonical URL points to origin-www.commcentric.com, not commcentric.com, so Google may credit that host instead.

Structured data found (WebSite) but with 1 problem, for example “WebSite: image is not an absolute URL ("//images.squarespace-cdn.com/content/v1/660c06a64e84f977448…”.

No XML sitemap at https://www.commcentric.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at commcentric.com/robots.txt, the first file search crawlers ask for.

Open Graph is missing og:description, so shared links fall back to guesses.

The homepage links to 21 pages on commcentric.com and 3 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.

/, /privacy-policy and /terms-of-use all use the title “CommCentric”. Search engines can't tell which page to show for a search, so each competes with the others.

/about-us, /our-work, /careers, /contact-us, /privacy-policy and /terms-of-use have no meta description, so Google writes the search snippet from whatever text it finds.

/about-us, /our-work, /careers, /contact-us, /privacy-policy and /terms-of-use have no <h1> headline, so visitors and search engines get no clear main topic.

/about-us and /contact-us have under 150 words in the HTML. Thin pages rarely rank; if the text loads with JavaScript, crawlers that don't run it see even less.

We fetched 6 pages linked from your homepage and read each the way a search engine does.

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

6 errors were logged to the browser console while the page loaded, for example “Loading the image 'https://www.googletagmanager.com/td?id=G-1JDZ5HW7MP&v=3&t=t&pid=1814777397&gtm=45je6b31v878658415za2…”.

1 link from your homepage to your own site is broken, for example https://www.commcentric.com/contact-us (network).

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

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.

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

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

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

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

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