onlinegrowthsystems.com website review

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

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

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

14 images could be 2.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Accessibe Accessibility Overlay and others), adding 1.5 MB and 865 ms of main-thread time.

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

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

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

Google CDN costs a phone 427 ms of main-thread work and 743 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 300 ms).

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

24 KiB could be saved by minifying JavaScript.

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

6 KiB could be saved by minifying CSS.

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

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.

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

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

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

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

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

3 images 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 10.5 MB in 153 requests on a phone: images 7.7 MB (67), scripts 2.0 MB (37) and other files 375 KiB (17). Under 2 MB keeps phones on slow connections fast.

28 images (2.1 MB) 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.

29 images further down the page (1.7 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

2 images are downloaded at several times the size a phone draws them, for example 1.png at 1,500 px wide, shown at 122 px. Resized copies would save about 197 KiB.

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

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

3 images have no alt text, which hurts accessibility and image search.

All page content should be contained by landmarks: 23 elements on the page fail this check, rated moderate by axe-core.

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

13 form fields have 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 21 characters: “Online Growth Systems”. Between 30 and 65 characters leaves room to say what you do and for whom.

1 link has no real href, so search engines can't follow it.

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

The homepage links to 139 pages on onlinegrowthsystems.com and 12 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.

https://onlinegrowthsystems.com/services, https://onlinegrowthsystems.com/service/ada-compliance-service, https://onlinegrowthsystems.com/service/animated-explainer-video-service, https://onlinegrowthsystems.com/service/audience-engagement-service, https://onlinegrowthsystems.com/service/blogging-service and https://onlinegrowthsystems.com/service/email-marketing-service and 5 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://onlinegrowthsystems.com/services, https://onlinegrowthsystems.com/service/ada-compliance-service, https://onlinegrowthsystems.com/service/animated-explainer-video-service, https://onlinegrowthsystems.com/service/audience-engagement-service, https://onlinegrowthsystems.com/service/blogging-service and https://onlinegrowthsystems.com/service/email-marketing-service and 6 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://onlinegrowthsystems.com/service/ada-compliance-service, https://onlinegrowthsystems.com/service/audience-engagement-service, https://onlinegrowthsystems.com/service/email-marketing-service, https://onlinegrowthsystems.com/service/social-media-video-service, https://onlinegrowthsystems.com/service/360-degree-camera-content-service and https://onlinegrowthsystems.com/app-managed-services took over 3 s to send their HTML from our server.

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

2 images failed to load on a phone, for example https://onlinegrowthsystems.com/wp-content/uploads/2-400x12402-400x1240/11/2-400x124.png.

3 of 7 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: the server responded with a status of 404 ()”.

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

Before a visitor clicks anything, the page loads Google Analytics, Google Tag Manager and X (Twitter) Ads (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 8 cookies, 2 of them by other companies (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 17 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.