pso-rite.com.co website review

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

Your mobile performance score is 75. Pages that score under 90 lose visitors before the first paint.

2 files block the first paint until they finish downloading. Deferring or inlining them could save about 450 ms.

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

8 third-party services load with your homepage (Google Tag Manager, userway.org and Shopify and others), adding 506 KiB and 265 ms of main-thread time.

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

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

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

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

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

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

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

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

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

1 element use ARIA attributes their role does not allow, which confuses screen readers.

Certain ARIA roles must contain particular children: 1 element on the page fails this check, rated critical by axe-core.

ARIA attributes must conform to valid values: 1 element on the page fails this check, rated critical by axe-core.

1 button has no accessible name, so screen readers announce just “button”.

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

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

ARIA input fields must have an accessible name: 2 elements on the page fail this check, rated serious by axe-core.

ARIA toggle fields must have an accessible name: 1 element on the page fails this check, rated serious by axe-core.

Interactive controls must not be nested: 1 element on the page fails this check, rated serious by axe-core.

1 tap target is too small or too close together to hit reliably with a finger.

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

All page content should be contained by landmarks: 1 element on the page fails this check, rated moderate by axe-core.

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

Elements marked as presentational should be consistently ignored: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is 71 characters, so Google will cut it off around 60: “PSO-RITE | PSO-MINI | MASAJEADOR | DOLOR DE ESPALDA – Pso Rite Colombia”.

There are 2 <h1> headlines (“Pso Rite Colombia” and “«¡GRACIAS POR CONTRIBUIR AL ÉXITO DE LOS PRODUCTO…”). One clear main headline is easier for people and search engines.

Your meta description is 272 characters; Google truncates after about 160, so the end of your pitch is cut.

Structured data found (Organization and Product) but with 1 problem, for example “Organization: url points at a different host (https://pso-rite.com)”.

The homepage links to 43 pages on pso-rite.com.co and 10 external pages.

https://pso-rite.com.co/products/pso-rite and https://pso-rite.com.co/collections/pso-rite-products/products/pso-rite all use the title “PSO-RITE | PSOAS ILÍACO | MASAJEADOR | DOLOR DE ESPALDA | ALIVIO MUSC…”, and 2 other titles repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://pso-rite.com.co/collections/all, https://pso-rite.com.co/policies/privacy-policy and https://pso-rite.com.co/policies/refund-policy have no meta description, so Google writes the search snippet from whatever text it finds.

https://pso-rite.com.co/products/pso-rite and https://pso-rite.com.co/collections/pso-rite-products/products/pso-rite use the same meta description. A description written for each page earns more clicks.

Your homepage links to 4 pages by a URL that isn't their canonical one, for example https://pso-rite.com.co/collections/pso-rite-products/products/pso-rite, whose canonical is https://pso-rite.com.co/products/pso-rite. Linking straight to the canonical URL saves crawlers a detour and keeps ranking signals on one address.

https://pso-rite.com.co/pages/modo-de-uso, https://pso-rite.com.co/pages/pso-rite-preguntas-frecuentes and https://pso-rite.com.co/pages/contacto have no <h1> headline, so visitors and search engines get no clear main topic.

https://pso-rite.com.co/collections/pso-rite-products, https://pso-rite.com.co/pages/modo-de-uso and https://pso-rite.com.co/collections/all have 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 19 found) and read each the way a search engine does.

1 error was logged to the browser console while the page loaded, for example “Uncaught SyntaxError: Invalid or unexpected token”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.

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

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

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 7 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 11 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.