pipamas.com website review

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

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

6 third-party services load with your homepage (YouTube, Google Tag Manager and Google Analytics and others), adding 1.5 MB and 889 ms of main-thread time.

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

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

YouTube costs a phone 595 ms of main-thread work and 1.0 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.

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

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

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

28 KiB could be saved by minifying JavaScript.

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

About 129 KiB of CSS is downloaded but never applied on this page.

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

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

4 KiB could be saved by minifying CSS.

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

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

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

Your largest element takes 4.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “PIPAMAS was established as the first manufacturer of oil an…”. Most of its time is element render delay (2.4 s).

Scripts block taps and scrolling for 349 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 2.4 MB in 99 requests on a phone: scripts 1.4 MB (35), images 466 KiB (14) and fonts 180 KiB (4). Under 2 MB keeps phones on slow connections fast.

1 image (31 KiB) is 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.

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

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

Links must have discernible text: 1 element on the page fails this check, rated serious by axe-core.

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

1 form field has 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.

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

There is no <h1>, so neither visitors nor Google get a clear main headline.

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

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

The homepage links to 31 pages on pipamas.com and 7 external pages.

There is no https://pipamas.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://pipamas.com/fluidizing-media, https://pipamas.com/oil-and-gas, https://pipamas.com/power-generation, https://pipamas.com/industrial, https://pipamas.com/octg-threading-service and https://pipamas.com/refining-petrochemical-process and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

Your homepage links to 1 page by a URL that isn't its canonical one, for example https://pipamas.com/refining, whose canonical is https://pipamas.com/refining-petrochemical. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://pipamas.com/fluidizing-media, https://pipamas.com/oil-and-gas, https://pipamas.com/power-generation, https://pipamas.com/industrial, https://pipamas.com/octg-threading-service and https://pipamas.com/refining-petrochemical-process and 9 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://pipamas.com/downhole-tools-accessories-2 has 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 24 found) and read each the way a search engine does.

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 of 8 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 “Failed to load resource: net::ERR_FAILED”.

Chrome logged issues while loading the page (“Cookie”).

No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

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