procurecircular.com website review

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

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

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

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

8 images could be 2.8 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

About 584 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 56. Pages that score under 90 lose visitors before the first paint.

111 KiB could be saved by minifying CSS.

6 third-party services load with your homepage (ZenDesk, Google Tag Manager and Clarity and others), adding 899 KiB and 511 ms of main-thread time.

ZenDesk costs a phone 219 ms of main-thread work and 430 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.

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

6 long tasks block the main thread while loading, the longest for 123 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).

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

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

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

Your largest element takes 7.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “SOURCE LOW IMPACT MATERIAL TO IMPROVE THE SUSTAINABILITY FO…”.

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

34 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 15.0 MB in 117 requests on a phone: images 12.6 MB (62), scripts 1.1 MB (23) and fonts 579 KiB (7). Under 2 MB keeps phones on slow connections fast.

3 images weigh 2.5 MB together. On a phone connection a single image that size takes seconds.

6 images are downloaded at several times the size a phone draws them, for example product-images.png at 1,534 px wide, shown at 342 px. Resized copies would save about 1.7 MB.

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

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

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

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

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

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

Headings skip levels (h2 → h5, h2 → h5 and h2 → h5), 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.

Your title is 81 characters, so Google will cut it off around 60: “Circular Textile Marketplace | B2B Sustainable Textile Platform | ProcureCircular”.

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

The homepage links to 78 pages on procurecircular.com and 9 external pages.

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.

/how-it-works, /resources/creating-a-circular-product-with-fairbank-textiles, /resources/life-cycle-assessment-lca-in-the-textile-industry-a-comprehensive-guide and /resources/the-new-era-of-compliance-espr-impact-on-the-textile-industry all use the title “ProcureCircular”. Search engines can't tell which page to show for a search, so each competes with the others.

/inspiration, /circular-marketplace, /how-it-works, /circular-freemium, /lca and /esg and 9 others have no meta description, so Google writes the search snippet from whatever text it finds.

/how-it-works, /resources/creating-a-circular-product-with-fairbank-textiles, /resources/life-cycle-assessment-lca-in-the-textile-industry-a-comprehensive-guide and /resources/the-new-era-of-compliance-espr-impact-on-the-textile-industry have no <h1> headline, so visitors and search engines get no clear main topic.

We fetched 15 pages linked from your homepage (of 19 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.

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

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

There is no form on the homepage, so every lead has to click through to another page first.

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

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 801 words of visible text.

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