productsup.com website review

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

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

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

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

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

8 third-party services load with your homepage (Cookiebot, Hubspot and Facebook and others), adding 1.2 MB and 3.0 s of main-thread time.

Cookiebot costs a phone 828 ms of main-thread work and 344 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.

Hubspot costs a phone 802 ms of main-thread work and 321 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.

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

Facebook costs a phone 474 ms of main-thread work and 224 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.

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

Hotjar costs a phone 382 ms of main-thread work and 65 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.

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

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

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.

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

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

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

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

Your largest element takes 8.1 s to render on a phone. Google's threshold for “good” is 2.5 s.

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 166 ms to 210 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

53 images have no width and height attributes, so the layout jumps as each one loads.

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

Your homepage downloads 11.4 MB in 226 requests on a phone: images 6.6 MB (127), media 2.5 MB (1) and scripts 2.0 MB (54). Under 2 MB keeps phones on slow connections fast.

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

10 images are downloaded at several times the size a phone draws them, for example AI_Channels__2_.png at 3,097 px wide, shown at 261 px. Resized copies would save about 2.9 MB.

24 images (4.2 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.

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

Productsup_Main_Hero.svg is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

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

Scrollable region must have keyboard access: 4 elements on the page fail this check, rated serious by axe-core.

1 image has no alt text, which hurts accessibility and image search.

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

Landmarks should have a unique role or role/label/title (i.e. accessible name) combination: 1 element on the page fails this check, rated moderate by axe-core.

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

Your title is 66 characters, so Google will cut it off around 60: “Productsup: Connecting commerce, powering performance | Productsup”.

There are 2 <h1> headlines (“Connecting commerce. Powering performance.” and “Connect your product content with 2500+ integrati…”). One clear main headline is easier for people and search engines.

No XML sitemap at https://www.productsup.com/sitemap.xml, so Google discovers your pages only by following links.

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

1 link has no real href, so search engines can't follow it.

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

The homepage links to 49 pages on productsup.com and 7 external pages.

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

/ and https://www.productsup.com/de all use the title “Productsup: Connecting commerce, powering performance | Productsup”. Search engines can't tell which page to show for a search, so each competes with the others.

https://www.productsup.com/ai-powered-product-content and https://www.productsup.com/privacy-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.productsup.com/de, https://www.productsup.com/feed-management, https://www.productsup.com/agentic-commerce, https://www.productsup.com/feed-management-for-marketplaces and https://www.productsup.com/product-content-syndication took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

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

Large scripts ship without source maps.

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.

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

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

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

The homepage shows no opening hours. If customers visit or call, show when.

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 1,005 words of visible text.

Before a visitor clicks anything, the page loads Google Ads, Google Tag Manager, Hotjar, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (Cookiebot) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 19 cookies (measured from a US location before any click).

Loading the homepage contacts 41 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.