phillipsind.com website review

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

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

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

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

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

8 third-party services load with your homepage (Google CDN, Google Tag Manager and Other Google APIs/SDKs and others), adding 3.7 MB and 734 ms of main-thread time.

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

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

7 images could be 513 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

Google CDN costs a phone 430 ms of main-thread work and 741 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.

assetcdn.net costs a phone 0 ms of main-thread work and 2.6 MB 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.

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

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

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

8 KiB could be saved by minifying CSS.

7 KiB could be saved by minifying JavaScript.

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.

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.

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

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

Your largest element takes 7.3 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “We Make Products that Make A Difference”.

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

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

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

Real visitors see the first content after 2.0 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.

52 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 95 ms to 108 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 1.6 s to 1.6 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

Your homepage downloads 58.4 MB in 309 requests on a phone: media 53.7 MB (30), images 2.7 MB (213) and scripts 1.2 MB (37). Under 2 MB keeps phones on slow connections fast.

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

399 elements have a tabindex above 0, which scrambles the keyboard order.

Some list items are not inside a list.

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

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

1 dropdown has no label.

Some lists contain elements other than list items, which screen readers announce wrongly.

6 elements hidden from screen readers can still receive keyboard focus.

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

2 tap targets are too small or too close together to hit reliably with a finger.

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

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

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

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

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

There are 6 <h1> headlines (“We Make Products that Make A Difference”, “A Global Leader in Innovation” and “95”). One clear main headline is easier for people and search engines.

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

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

The homepage links to 550 pages on phillipsind.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.

There is no /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.

/product/sta-dry-qcms2 and /product/sta-dry-qcms2-2 all use the title “STA-DRY® QCMS2™ - Phillips Ind”. Search engines can't tell which page to show for a search, so each competes with the others.

/product-category/electrical-assemblies-2, /product-category/electrical-assemblies-2/coiled-assemblies-electric-assemblies, /product/isocoil, /product/duracoil, /product/abs-lectracoil and /product/non-abs-permacoil and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/product-category/electrical-assemblies-2, /product-category/electrical-assemblies-2/coiled-assemblies-electric-assemblies, /product/isocoil, /product/duracoil, /product/abs-lectracoil and /product/non-abs-permacoil and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

/product-category/electrical-assemblies-2/coiled-assemblies-electric-assemblies, /product/isocoil, /product/duracoil, /product/abs-lectracoil, /product/non-abs-permacoil and /product/coiled-m7 and 5 others took over 3 s to send their HTML from our server.

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

1 error was logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

X-Content-Type-Options: nosniff is missing, so browsers may guess file types.

X-XSS-Protection is set to “1”; the header is deprecated and can introduce bugs. Use 0 or remove it.

There is no /.well-known/security.txt telling researchers how to report a security problem to you.

phillipsind.com has no CAA record, so any certificate authority may issue a certificate for it. A CAA record naming your provider (for example letsencrypt.org) closes that door.

phillipsind.com's DNS answers are not signed. DNSSEC stops attackers forging them to send visitors or email elsewhere; most registrars switch it on in a click, though most sites still run without it.

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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 3,162 words of visible text.

Email authentication: SPF record 25 points, plus 15 when it ends in -all (10 for ~all); DMARC record 25, plus 25 for a reject policy (15 for quarantine); a DKIM key on a common selector 10.

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