pcgus.com website review

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

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

YouTube costs a phone 1.6 s of main-thread work and 3.6 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 29 (desktop: 82). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

Google CDN costs a phone 365 ms of main-thread work and 734 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 376 ms. During a long task the page ignores taps.

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

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

5 KiB could be saved by minifying JavaScript.

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

Desktop scores 82 but mobile only 29. A gap that wide usually means heavy scripts and images that hit phones hardest.

Polyfills for old browsers add 9 KiB JavaScript that modern phones do not need.

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.

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

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

Your largest element takes 30.8 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Three people collaborating in front of a whiteboard”.

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 83 ms to 87 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 1.8 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 7.2 MB in 167 requests on a phone: scripts 4.2 MB (39), images 1.3 MB (45) and fonts 538 KiB (18). Under 2 MB keeps phones on slow connections fast.

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

8 images (369 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.

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

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

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

1 form field has no label, so screen readers announce an empty box and autofill guesses.

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Elements with visible text labels do not have matching accessible names. (1 element).

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

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

The homepage links to 88 pages on pcgus.com and 4 external pages.

https://publicconsultinggroup.com/insights and https://publicconsultinggroup.com/focus-areas declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

/, https://publicconsultinggroup.com/insights and https://publicconsultinggroup.com/focus-areas all use the title “Solutions That Matter | PCG | Public Consulting Group”. Search engines can't tell which page to show for a search, so each competes with the others.

https://publicconsultinggroup.com/insights and https://publicconsultinggroup.com/focus-areas use the same meta description. A description written for each page earns more clicks.

https://publicconsultinggroup.com/insights, https://publicconsultinggroup.com/insights/category/solutions-in-action, https://publicconsultinggroup.com/insights/category/news-media, https://publicconsultinggroup.com/insights/category/people-perspectives and https://publicconsultinggroup.com/focus-areas have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

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

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

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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.

No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

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

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 2,021 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics and Google Tag Manager (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 6 cookies, 1 of them by other companies (measured from a US location before any click).

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