musajisons.com website review

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

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

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

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

Your mobile performance score is 58 (desktop: 84). Pages that score under 90 lose visitors before the first paint.

8 third-party services load with your homepage (Google Tag Manager, jQuery CDN and getbutton.io and others), adding 905 KiB and 517 ms of main-thread time.

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

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

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

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

34 KiB could be saved by minifying JavaScript.

12 KiB JavaScript is shipped twice across bundles.

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

Polyfills for old browsers add 10 KiB JavaScript that modern phones do not need.

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

2 KiB could be saved by minifying CSS.

Your largest element takes 6.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “your single source ... for LABORATORY SUPPLIES”. Most of its time is element render delay (2.8 s).

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

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

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

80 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.2 MB in 115 requests on a phone: images 1.9 MB (56), scripts 1.1 MB (30) and stylesheets 100 KiB (17). Under 2 MB keeps phones on slow connections fast.

15 images (1.0 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.

28 images further down the page (878 KiB) 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 experts.jpg at 1,160 px wide, shown at 360 px. Resized copies would save about 30 KiB.

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

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

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

1 element hidden from screen readers can still receive keyboard focus.

Elements must only use permitted ARIA attributes: 1 element on the page fails this check, rated serious by axe-core.

1 frame has no title, so screen-reader users cannot tell what it contains.

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

7 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

ARIA role should be appropriate for the element: 2 elements on the page fail this check, rated minor by axe-core.

Elements marked as presentational should be consistently ignored: 2 elements on the page fail this check, rated minor by axe-core.

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

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

There are 6 <h1> headlines (“MICROBIOLOGY”, “LABWARE” and “CHEMICALS”). One clear main headline is easier for people and search engines.

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://musajisons.com/sitemap.xml, so Google discovers your pages only by following links.

There is no robots.txt at musajisons.com/robots.txt, the first file search crawlers ask for.

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

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

The homepage links to 29 pages on musajisons.com and 3 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://musajisons.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://musajisons.com/microbiology.html, https://musajisons.com/foodsafety.html, https://musajisons.com/lifescience.html, https://musajisons.com/labchemicals.html, https://musajisons.com/labequipment.html and https://musajisons.com/labglassware.html and 7 others all use the title “Document”. Search engines can't tell which page to show for a search, so each competes with the others.

https://musajisons.com/company.html, https://musajisons.com/microbiology.html, https://musajisons.com/foodsafety.html, https://musajisons.com/lifescience.html, https://musajisons.com/labchemicals.html and https://musajisons.com/labequipment.html and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://musajisons.com/microbiology.html, https://musajisons.com/foodsafety.html, https://musajisons.com/lifescience.html, https://musajisons.com/labchemicals.html, https://musajisons.com/labequipment.html and https://musajisons.com/labglassware.html and 8 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://musajisons.com/lifescience.html, https://musajisons.com/labchemicals.html, https://musajisons.com/labequipment.html, https://musajisons.com/labglassware.html, https://musajisons.com/rawmaterial.html and https://musajisons.com/labfiltration.html and 3 others have 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 15 pages linked from your homepage (of 16 found) and read each the way a search engine does.

1 image failed to load on a phone, for example https://musajisons.com/img/logo.png.

4 errors were logged to the browser console while the page loaded, for example “Not allowed to load local resource: file:///C:/Users/msadler/Desktop/slick-1.5.7/slick/fonts/slick.woff”.

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

1 image is served at too low a resolution for sharp phone screens.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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

The homepage has only about 95 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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