jariollano.com website review

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

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

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

8 third-party services load with your homepage (Shopify, Google CDN and Stamped.io and others), adding 14.4 MB and 877 ms of main-thread time.

Shopify costs a phone 782 ms of main-thread work and 14.1 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.

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

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

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

37 KiB could be saved by minifying JavaScript.

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

About 47 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.

4 KiB could be saved by minifying CSS.

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

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

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

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

Over the last 25 four-week periods to 2026-11-07, real Chrome visitors' largest content (lcp) went from 1.4 s to 1.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

Your homepage downloads 22.7 MB in 384 requests on a phone: media 16.5 MB (5), images 3.0 MB (56) and scripts 1.9 MB (154). Under 2 MB keeps phones on slow connections fast.

19 images are downloaded at several times the size a phone draws them, for example 5oferta_portada.png at 1,800 px wide, shown at 181 px. Resized copies would save about 1.5 MB.

1 image (140 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.

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

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

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

Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.

54 form fields have no label, so screen readers announce an empty box and autofill guesses.

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

Alternative text of images should not be repeated as text: 3 elements on the page fail this check, rated minor by axe-core.

Elements with visible text labels do not have matching accessible names. (6 elements).

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

Your title is 111 characters, so Google will cut it off around 60: “JA Riollano Co, Inc. School I Office I Crafts I Copies – JA Riollano Co, Inc. School I Of…”.

No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.

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

The homepage links to 112 pages on jariollano.com and 6 external pages.

There is no Organization (or LocalBusiness) JSON-LD, so search engines and AI assistants have no machine-readable facts about who runs the site: its name, logo, profiles and contact details.

https://jariollano.com/pages/mi-lista-de-deseos, https://jariollano.com/collections/articulos-de-oficina-1, https://jariollano.com/collections/articulos-escolares-1, https://jariollano.com/collections/arte-y-manualidades-1, https://jariollano.com/collections/juguetes-educativos-1 and https://jariollano.com/collections/decoracion and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://jariollano.com/collections/articulos-de-oficina-1, https://jariollano.com/collections/articulos-escolares-1, https://jariollano.com/collections/arte-y-manualidades-1, https://jariollano.com/collections/juguetes-educativos-1, https://jariollano.com/collections/decoracion and https://jariollano.com/collections/libros-y-diccionarios-1 and 3 others have no <h1> headline, so visitors and search engines get no clear main topic.

https://jariollano.com/collections/articulos-de-oficina-1, https://jariollano.com/collections/articulos-escolares-1, https://jariollano.com/collections/arte-y-manualidades-1, https://jariollano.com/collections/juguetes-educativos-1, https://jariollano.com/collections/decoracion and https://jariollano.com/collections/libros-y-diccionarios-1 and 2 others 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.

https://jariollano.com/pages/marcas, https://jariollano.com/pages/programa-de-descuentos, https://jariollano.com/pages/ayuda and https://jariollano.com/pages/contactanos took over 3 s to send their HTML from our server.

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

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

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.

Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.

No analytics or tag manager detected in the HTML, so you can't measure whether any of these fixes work.

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

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