insignialearning.com website review

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

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

2 images could be 379 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 2.0 s faster on a phone.

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

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

About 79 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 450 ms faster on a phone.

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

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

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

4 third-party services load with your homepage (Google Fonts, FontAwesome CDN and Cloudflare CDN and others), adding 416 KiB and 0 ms of main-thread time.

Desktop scores 63 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.

5 KiB could be saved by minifying CSS.

Your largest element takes 20.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “The Future Of Medical Affairs Is Conversational Learn More”.

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

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

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

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

65 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 3.4 MB in 93 requests on a phone: images 2.7 MB (67), fonts 441 KiB (8) and scripts 182 KiB (8). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example mapv4.png at 1,900 px wide, shown at 390 px. Resized copies would save about 55 KiB.

2 images (403 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.

5 images further down the page (218 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 0.97 g of CO₂e: 116.1 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

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

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

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.

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

7 form fields have 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 (h1 → h3, h1 → h4 and h3 → h5), which makes the page harder to scan with a screen reader.

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

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

Your meta description is only 24 characters: “Home - Insignia Learning”. 70 to 160 characters is enough to sell the click.

There are 8 <h1> headlines (“8+”, “500+” and “150+”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

4 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 82 pages on insignialearning.com and 20 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 https://insignialearning.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.

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

Chrome logged issues while loading the page (“Content security policy”).

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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

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