Website review, no card needed
onlineprocurement.eu website review
Visit site (opens in a new tab)Reviewed 8 November 202625 issues · 74 checks
This review found 25 issues worth fixing on onlineprocurement.eu, 8 of them high impact, across 74 checks. The most urgent: reduce unused JavaScript. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
82BClosest competitors among reviewed websites
Compare side by sideOne score from every part of this review. How it works
How it loaded on a phone
1.2 s
2.4 s
3.6 s
4.8 s
6.0 s
7.2 s
8.3 s
9.5 s
Speed
Reduce unused JavaScript
2.0 s · 483 KiBAbout 483 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 2.0 s faster on a phone.
Render-blocking requests
2.3 s8 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.3 s.
Mobile performance score: 67
67/100Your mobile performance score is 67. Pages that score under 90 lose visitors before the first paint.
Font display
750 msWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 750 ms).
Reduce unused CSS
600 ms · 140 KiBAbout 140 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 600 ms faster on a phone.
5 third-party services on the page
5 third-party services load with your homepage (digitalpa.it, Google CDN and Other Google APIs/SDKs and others), adding 1.0 MB and 199 ms of main-thread time.
1,712 HTML elements
The page has 1,712 HTML elements. Above 1,500, rendering and every interaction get slower on phones.
Google CDN adds 73 ms
73 msGoogle CDN costs a phone 73 ms of main-thread work and 349 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.
FontAwesome CDN adds 0 ms
0 msFontAwesome CDN costs a phone 0 ms of main-thread work and 376 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.
2 long tasks on the main thread
2 long tasks block the main thread while loading, the longest for 84 ms. During a long task the page ignores taps.
Improve image delivery
27 KiB4 images could be 27 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.
Legacy JavaScript
11 KiBPolyfills for old browsers add 11 KiB JavaScript that modern phones do not need.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
Use efficient cache lifetimes
4 KiB4 files are served with short cache lifetimes, so returning visitors download them again (4 KiB).
2 checks passed
Main-thread work: 1.9 s
A phone's processor spends 1.9 s on main-thread work while loading, 419 ms of it running JavaScript. That is comfortably low.
Server response: 126 ms
126 msYour server sent the HTML in 126 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Largest Contentful Paint: 9.9 s
9.9 sYour largest element takes 9.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “online-procurement-software-digitalizzazione-acquisti-”. Most of its time is resource load delay (4.0 s).
Time to Interactive: 11.7 s
11.7 sThe page becomes fully interactive after 11.7 s. Good is under 3.8 s.
Speed Index: 7.9 s
7.9 sVisually, the page fills in at 7.9 s (Speed Index). Good is under 3.4 s.
1 image without width and height
1 image have no width and height attributes, so the layout jumps as each one loads.
Not enough real-visitor data yet
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.
3 checks passed
First Contentful Paint: 1.1 s
1.1 sThe first text or image appears after 1.1 s, inside the 1.8 s “good” threshold.
Cumulative Layout Shift: 0.011
0.011The layout barely moves while loading (CLS 0.011, good is under 0.1).
Total Blocking Time: 32 ms
32 msScripts block the page for only 32 ms while loading. Good is under 200 ms.
Images and page weight
Page weight: 2.6 MB in 59 requests
2.6 MBYour homepage downloads 2.6 MB in 59 requests on a phone: scripts 814 KiB (13), media 792 KiB (1) and fonts 493 KiB (15). Under 2 MB keeps phones on slow connections fast.
1 image in older formats
1 image (53 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.
About 0.7 g of CO₂ per visit
0.74 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.74 g of CO₂e: 88.7 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
2 checks passed
Images load when needed
Images below the first screen wait until the visitor scrolls to them.
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
16 text elements with low contrast
16 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
Frames without titles
1 frame has no title, so screen-reader users cannot tell what it contains.
All page content should be contained by landmarks (16 elements)
All page content should be contained by landmarks: 16 elements on the page fail this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
2 checks passed
Every image has alt text
All 56 images in the HTML carry an alt attribute.
45 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 50 WCAG 2.2 A/AA and best-practice rules on the phone render: 45 passed and 5 failed. 3 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
Title is long (74 characters)
Your title is 74 characters, so Google will cut it off around 60: “Online Procurement software la soluzione digitale per la gestione acquisti”.
219 internal links, 14 external
The homepage links to 219 pages on onlineprocurement.eu and 14 external pages.
7 checks passed
Meta description: 139 characters
Your meta description is 139 characters: “Online Procurement software è la suite modulare per la completa digitalizzazione dei processi di acquisto aziendali e l…”.
One H1 headline
Your main headline reads: “Online Procurement, la piattaforma next-levelper aziende innovative”.
Canonical URL set
The canonical URL is https://www.onlineprocurement.com/.
Structured data in place
Structured data found: BreadcrumbList, ImageObject, Organization, SoftwareApplication and WebPage.
Open Graph tags complete
Open Graph tags are complete, so shared links show a title, description and image.
robots.txt in place
robots.txt is in place and points crawlers to your sitemap.
XML sitemap found
Your XML sitemap is reachable at https://www.onlineprocurement.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing sameAs (social profiles), description and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (1,426 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.onlineprocurement.com/llms.txt (10 KiB, 85 links), a plain-text guide to the site for AI tools.
Other pages
1 link to non-canonical URLs
Your homepage links to 1 page by a URL that isn't its canonical one, for example https://www.onlineprocurement.com/rassegna-stampa-software-e-procurement, whose canonical is https://www.onlineprocurement.com/it/rassegna-stampa-software-e-procurement. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 53 found) and read each the way a search engine does.
6 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Every page has a meta description
All 15 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
Every page has an H1
Each page we checked has a main headline.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 15 pages that loaded have a <title>.
Best practices
8 small tap targets
8 of 33 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
1 low-resolution image
1 image is served at too low a resolution for sharp phone screens.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
About 1,061 words of copy
The homepage carries about 1,061 words of visible text.
5 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “Richiedi una Demo” and “Demo”.
8 calls to action
The homepage has 8 calls to action, for example “DEMO”, “Richiedi una demo” and “Richiedi una Demo”.
1 short form
A short form (1 field at most) is right on the homepage.
Social proof on the page
Social proof on the homepage: 4 testimonial or review blocks, a star rating and 3 trust badges.
Analytics in place
Analytics detected: Matomo.
Privacy and tracking
1 cookie set on arrival
1Opening the homepage sets 1 cookie (measured from a US location before any click).
No consent tool detected
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.
6 other companies contacted
Loading the homepage contacts 6 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
1 checks passed
No known trackers before consent
No known advertising or analytics trackers load before a visitor clicks anything (measured from a US location before any click).
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at onlineprocurement.eu, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- CMS
- WordPress
- Analytics
- Matomo
- Hosting
- Aruba S.p.A.
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 25 issues on onlineprocurement.eu, including 13 speed issues, 1 SEO issue and 1 conversion gap. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.