tinystork.com.ar website review

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

Web fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.2 s).

14 images could be 994 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.

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

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

6 third-party services load with your homepage (Google CDN, Other Google APIs/SDKs and esmsv.com and others), adding 3.5 MB and 402 ms of main-thread time.

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

Google CDN costs a phone 301 ms of main-thread work and 743 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.

esmsv.com costs a phone 36 ms of main-thread work and 2.5 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.

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

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

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

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.

2 KiB could be saved by minifying CSS.

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

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

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

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

The layout shifts by 0.228 while loading, so content jumps under the reader's thumb. Good is under 0.1.

1 image 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 3.9 MB in 58 requests on a phone: images 1.4 MB (19), fonts 1.1 MB (8) and scripts 881 KiB (17). Under 2 MB keeps phones on slow connections fast.

1 image is downloaded at several times the size a phone draws it, for example DSCN6058_uFyCE7lJqT_qlYU8uRSWf.webp at 1,855 px wide, shown at 290 px. Resized copies would save about 72 KiB.

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

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

Inline text spacing must be adjustable with custom stylesheets: 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.

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

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

Contentinfo landmark should not be contained in another landmark: 1 element on the page fails this check, rated moderate by axe-core.

Document should not have more than one contentinfo landmark: 1 element on the page fails 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.

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

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

Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.

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

Your title is only 4 characters: “Home”. Between 30 and 65 characters leaves room to say what you do and for whom.

There are 2 <h1> headlines (“Regalos personalizados” and “Nuestro trabajo”). One clear main headline is easier for people and search engines.

Structured data found (Organization and WebSite) but with 2 problems, for example “Organization: logo is not an absolute URL ("https://ss-cnt-001c.esmsv.com/r/content/host1/b6320c584…”.

The homepage links to 22 pages on tinystork.com.ar and 8 external pages.

We fetched 2 pages linked from your homepage and read each the way a search engine does.

3 of 7 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.

2 errors were logged to the browser console while the page loaded, for example “Access to XMLHttpRequest at 'https://ss-cnt-001c.esmsv.com/r/content/host1/b6320c5849344bd6f60ae0ab393ccbeb/css/TdtGHeJ…”.

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 testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.

Your homepage shows a map but no LocalBusiness JSON-LD, so Google and AI assistants have to guess your address, hours and phone from the page text.

The homepage has only about 119 words of visible text; thin pages give Google and first-time buyers little to go on.

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

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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