pugetsystems.com website review

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

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

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

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

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

Google Tag Manager costs a phone 807 ms of main-thread work and 810 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.

Hotjar costs a phone 384 ms of main-thread work and 257 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.

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

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

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

Facebook costs a phone 265 ms of main-thread work and 222 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 244 ms of main-thread work and 316 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 273 ms. During a long task the page ignores taps.

FontAwesome CDN costs a phone 187 ms of main-thread work and 661 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.

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

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

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

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.

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

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

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

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

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

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

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

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

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

Your homepage downloads 7.7 MB in 154 requests on a phone: media 2.9 MB (1), scripts 2.4 MB (56) and images 845 KiB (32). Under 2 MB keeps phones on slow connections fast.

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

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

4 images are downloaded at several times the size a phone draws them, for example AI_HPC.jpg at 1,160 px wide, shown at 328 px. Resized copies would save about 137 KiB.

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

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

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

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

Structured data found (BreadcrumbList, ImageObject, Organization and Service) but with 1 problem, for example “Service: no offers (price) block”.

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

The homepage links to 165 pages on pugetsystems.com and 8 external pages.

There is no https://www.pugetsystems.com/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.

https://www.pugetsystems.com/solutions, https://www.pugetsystems.com/solutions/media-and-entertainment-workstations, https://www.pugetsystems.com/solutions/photo-editing-workstations/adobe-lightroom-classic, https://www.pugetsystems.com/solutions/photo-editing-workstations/adobe-photoshop and https://www.pugetsystems.com/solutions/video-editing-workstations/adobe-premiere-pro took over 3 s to send their HTML from our server.

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

The page uses 2 deprecated browser APIs that will stop working in future browsers (“`StorageType.persistent` is deprecated. Please use standardized `navigator.storage` instead.”).

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

Social proof on the homepage: 1 customer or partner logo. Pairing it with named testimonials or customer logos makes it far more convincing.

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

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

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