mulphilog.com website review

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

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

About 1.9 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.5 s faster on a phone.

About 432 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 2.1 s faster on a phone.

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

1.1 MB could be saved by minifying JavaScript.

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

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

7 third-party services load with your homepage (Google Tag Manager, Facebook and JSDelivr CDN and others), adding 585 KiB and 248 ms of main-thread time.

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

Polyfills for old browsers add 23 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.

Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.

2 KiB could be saved by minifying CSS.

Real Chrome users on phones do not pass Google's Core Web Vitals on this page (28-day field data from the Chrome UX Report (opens in a new tab)). Google uses this in ranking.

Your largest element takes 15.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Building Stronger Connections with Innovative Global Soluti…”.

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

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

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

Real visitors wait 3.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.

Real visitors wait 264 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

Real visitors see the first content after 2.6 s (75th percentile). Good is under 1.8 s.

Real visitors wait 1.6 s for your server to start answering (75th percentile). Good is under 800 ms.

37 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' tap response (inp) went from 159 ms to 152 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.1 s to 2.1 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 9.1 MB in 71 requests on a phone: images 4.9 MB (42), scripts 3.0 MB (11) and fonts 633 KiB (13). Under 2 MB keeps phones on slow connections fast.

2 images weigh 3.0 MB together. On a phone connection a single image that size takes seconds.

20 images (3.8 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.

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

5 images are downloaded at several times the size a phone draws them, for example Glhc2kXX05yE1ABWpusyYK91UqIsht9L7xIwJbr4.png at 512 px wide, shown at 70 px. Resized copies would save about 286 KiB.

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

1 dropdown has no label.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

All page content should be contained by landmarks: 33 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 viewport tag blocks pinch-zoom, which low-vision visitors rely on.

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

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

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 49 pages on mulphilog.com and 14 external pages.

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

Your homepage links to https://www.mulphilog.com/careers, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.mulphilog.com/about-us/our-leadership, https://www.mulphilog.com/about-us/timeline and https://www.mulphilog.com/about-us/locations declare the homepage as their canonical URL, which tells Google they are copies of the homepage and keeps them out of search results. A site-wide template setting usually causes this.

https://www.mulphilog.com/contact-us has no meta description, so Google writes the search snippet from whatever text it finds.

https://www.mulphilog.com/contact-us, https://www.mulphilog.com/about-us/our-leadership, https://www.mulphilog.com/about-us/timeline, https://www.mulphilog.com/about-us/locations, https://www.mulphilog.com/about-us/life-at-m&p and https://www.mulphilog.com/courier and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

8 of 12 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 “Error: <svg> attribute viewBox: Expected number, "0 0 40px 40px".”.

9 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.

Large scripts ship without source maps.

Your longest form asks for 13 fields (0 required). Every extra field lowers completion.

The homepage has only about 122 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 4 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 7 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.