tapiabrothers.com website review

About 1.6 MB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 10.6 s faster on a phone.

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

About 259 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.2 s faster on a phone.

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

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

Your mobile performance score is 54 (desktop: 58). Pages that score under 90 lose visitors before the first paint.

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

YouTube costs a phone 399 ms of main-thread work and 987 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.

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

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

The HTML itself could arrive sooner: redirects, a slow server response or missing compression delay everything after it.

7 KiB could be saved by minifying JavaScript.

Google Tag Manager costs a phone 221 ms of main-thread work and 469 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.

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

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.

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

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

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

Your largest element takes 41.0 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “THE BROTHERS YOU CAN TRUST”.

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

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

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

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

Your homepage downloads 9.8 MB in 158 requests on a phone: images 5.0 MB (56), scripts 3.2 MB (44) and HTML 577 KiB (4). Under 2 MB keeps phones on slow connections fast.

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

1 image is downloaded at several times the size a phone draws it, for example 1897392.jpg at 3,183 px wide, shown at 278 px. Resized copies would save about 900 KiB.

9 images (2.0 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.

15 images further down the page (448 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

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

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

Form elements should have a visible label: 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.

All page content should be contained by landmarks: 16 elements on the page fail 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.

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

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

No meta description, so Google writes its own snippet from whatever text it finds.

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

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

No XML sitemap at https://tapiabrothers.yayestudio.com/?feed=xmlsitemap33, so Google discovers your pages only by following links.

The homepage links to 61 pages on tapiabrothers.com and 14 external pages.

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.

Your homepage links to https://tapiabrothers.com/buscar-productos, which answers with an error. Visitors hit a dead end and search engines drop it.

https://tapiabrothers.com/blog, https://tapiabrothers.com/our-products, https://tapiabrothers.com/our-story, https://tapiabrothers.com/our-partners, https://tapiabrothers.com/careers and https://tapiabrothers.com/order and 8 others have no meta description, so Google writes the search snippet from whatever text it finds.

https://tapiabrothers.com/blog, https://tapiabrothers.com/our-products, https://tapiabrothers.com/our-story, https://tapiabrothers.com/our-partners, https://tapiabrothers.com/order and https://tapiabrothers.com/maywood and 7 others have no <h1> headline, so visitors and search engines get no clear main topic.

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

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

5 third-party cookies are set on load; browsers are restricting these, so whatever relies on them breaks.

4 errors were logged to the browser console while the page loaded, for example “Failed to load resource: the server responded with a status of 402 ()”.

Chrome logged issues while loading the page (“Cookie”).

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

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

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

There is no link to Google or Apple Maps. A directions link is one tap for a phone visitor.

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