msigeneral.com website review

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

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

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

71 images could be 3.4 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 700 ms faster on a phone.

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

8 third-party services load with your homepage (Google Tag Manager, Facebook and Hubspot and others), adding 865 KiB and 656 ms of main-thread time.

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

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

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

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

15 KiB could be saved by minifying JavaScript.

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

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

Desktop scores 72 but mobile only 45. 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.

Your largest element takes 20.6 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 21.9 s. Good is under 3.8 s.

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

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

71 images have no width and height attributes, so the layout jumps as each one loads.

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

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.5 MB in 159 requests on a phone: images 4.1 MB (82), scripts 1.1 MB (36) and HTML 182 KiB (1). Under 2 MB keeps phones on slow connections fast.

24 images are downloaded at several times the size a phone draws them, for example DH-Industries-Logo.jpg at 1,000 px wide, shown at 195 px. Resized copies would save about 1.3 MB.

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

2 images (119 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 1.57 g of CO₂e: 187.8 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

All page content should be contained by landmarks: 21 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.

The skip-link target should exist and be focusable: 1 element on the page fails this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

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

There are 2 <h1> headlines (“Designing Excellence.” and “Building Trust.”). One clear main headline is easier for people and search engines.

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

4 links have no real href, so search engines can't follow them.

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

The homepage links to 172 pages on msigeneral.com and 4 external pages.

Your Organization JSON-LD is missing sameAs (social profiles), description 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://msigeneral.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://msigeneral.com/project-portfolio/awards-recognitions and https://msigeneral.com/visions-built/awards-recognitions all use the title “Awards & Recognitions | MSI General”. Search engines can't tell which page to show for a search, so each competes with the others.

https://msigeneral.com/project-portfolio/awards-recognitions and https://msigeneral.com/visions-built/awards-recognitions use the same meta description. A description written for each page earns more clicks.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://msigeneral.com/visions-built/awards-recognitions, whose canonical is https://msigeneral.com/project-portfolio/awards-recognitions. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

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

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

4 errors were logged to the browser console while the page loaded, for example “Uncaught TypeError: Cannot read properties of undefined (reading 'msie')”.

3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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.

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

The homepage carries about 3,122 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and Meta Pixel (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 9 cookies (measured from a US location before any click).

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