sagacom.com website review

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

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

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

Your mobile performance score is 54. Pages that score under 90 lose visitors before the first paint.

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

7 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 1,021 KiB and 815 ms of main-thread time.

17 images could be 352 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 450 ms faster on a phone.

Google CDN costs a phone 579 ms of main-thread work and 741 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.

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

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

Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.

5 KiB could be saved by minifying JavaScript.

2 KiB could be saved by minifying CSS.

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

Your largest element takes 12.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We believe in local media. At Saga Communications, we belie…”.

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

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

16 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' largest content (lcp) went from 1.5 s to 1.5 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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.6 MB in 61 requests on a phone: media 3.3 MB (2), scripts 997 KiB (19) and images 724 KiB (22). Under 2 MB keeps phones on slow connections fast.

2 images are downloaded at several times the size a phone draws them, for example angela-2.png at 300 px wide, shown at 80 px. Resized copies would save about 46 KiB.

4 images (192 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.

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

By the Sustainable Web Design model, a visit to your homepage emits about 1.58 g of CO₂e: 189.4 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.

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

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

Your title is only 26 characters: “Home - Saga Communications”. Between 30 and 65 characters leaves room to say what you do and for whom.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 13 pages on sagacom.com and 17 external pages.

Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.

There is no https://sagacom.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.

robots.txt blocks CCBot, which collect pages to train models. That's a legitimate choice and doesn't by itself stop the site appearing in AI answers, which the crawlers above handle.

https://sagacom.com/stations, https://sagacom.com/careers and https://sagacom.com/category/community-relations have no meta description, so Google writes the search snippet from whatever text it finds.

https://sagacom.com/careers has 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 8 pages linked from your homepage and read each the way a search engine does.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Social proof on the homepage: “more than 100 brands”. Pairing it with named testimonials or customer logos makes it far more convincing.

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

There is no form on the homepage, so every lead has to click through to another page first.

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

Before a visitor clicks anything, the page loads 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.

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