sushipop.com.ar website review

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

Google Tag Manager costs a phone 1.2 s of main-thread work and 541 KiB of downloads while your page loads. That alone is enough to make taps feel slow. Loading it after the page is usable, or only on the pages that need it, takes that off the critical path.

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

21 files are served with short cache lifetimes, so returning visitors download them again (5.1 MB).

8 third-party services load with your homepage (Google Tag Manager, Google CDN and Google Maps and others), adding 1.6 MB and 2.8 s of main-thread time.

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

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

Google CDN costs a phone 734 ms of main-thread work and 382 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 759 KiB of JavaScript is downloaded but never used on this page.

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

Google Maps costs a phone 407 ms of main-thread work and 406 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.

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

The page has 2,878 HTML elements. Above 1,500, rendering and every interaction get slower on phones.

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

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

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.

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

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

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

Real visitors wait 205 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.

For real visitors the layout shifts by 0.19 (75th percentile). Good is under 0.1.

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

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

Your largest element takes 3.6 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Imagen de combos spring”.

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

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

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

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

Your homepage downloads 6.4 MB in 84 requests on a phone: images 4.7 MB (47), scripts 1.6 MB (17) and fonts 49 KiB (2). Under 2 MB keeps phones on slow connections fast.

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

5 images (4.5 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.

1 image is downloaded at several times the size a phone draws it, for example S6w-buk5TpeQmJr-sgdxu6seM5l-X2tF.jpg at 1,080 px wide, shown at 94 px. Resized copies would save about 421 KiB.

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

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

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

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

Some lists contain elements other than list items, which screen readers announce wrongly.

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

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

The page has no <main> landmark, so screen-reader users cannot jump straight to the content.

The viewport tag blocks pinch-zoom, which low-vision visitors rely on.

Headings should not be empty: 21 elements on the page fail this check, rated minor by axe-core.

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

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

209 links have no real href, so search engines can't follow them.

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

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

There are 14 <h1> headlines (“Estamos cerrados. Abrimos a las 11:00”, “Combos Spring” and “Promos imperdibles”). One clear main headline is easier for people and search engines.

No canonical URL, so duplicate versions of the homepage (with or without www, with tracking parameters) can split ranking signals.

No Open Graph image (also missing: og:title, og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.

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

No favicon is declared in the HTML, so browser tabs and Google's mobile results may show a generic icon.

No twitter:card tag. X falls back to Open Graph, which is incomplete here.

The homepage links to 32 pages on sushipop.com.ar and 11 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.

There is no https://sushipop.com.ar/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.

https://sushipop.com.ar/franquicias, https://sushipop.com.ar/locales, https://sushipop.com.ar/site/recompensa-pop-faq, https://sushipop.com.ar/delivery, https://sushipop.com.ar/beneficios and https://sushipop.com.ar/legales and 3 others have no meta description, so Google writes the search snippet from whatever text it finds.

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

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

On a 390 px-wide phone the page scrolls sideways, a sign that something is wider than the screen.

1 image is served at too low a resolution for sharp phone screens.

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.

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

Your longest form asks for 46 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.

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