pastelescid.com website review

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

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

5 images could be 1.0 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen.

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

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

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

1 long task block the main thread while loading, the longest for 58 ms. During a long task the page ignores taps.

About 31 KiB of JavaScript is downloaded but never used on this page.

1 third-party service load with your homepage (Google Fonts), adding 71 KiB and 1 ms of main-thread time.

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.

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

Your largest element takes 2.9 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Disfruta de los mejores pasteles y postres en nuestra paste…”. Most of its time is element render delay (1.3 s).

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

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.

1-768x768.png weighs 668 KiB. On a phone connection a single image that size takes seconds.

Your homepage downloads 2.3 MB in 72 requests on a phone: images 1.5 MB (15), fonts 326 KiB (10) and stylesheets 252 KiB (24). Under 2 MB keeps phones on slow connections fast.

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

2 images are downloaded at several times the size a phone draws them, for example 1-768x768.png at 390 px wide, shown at 120 px. Resized copies would save about 219 KiB.

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

17 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: 5 elements on the page fail this check, rated moderate by axe-core.

1 visible link has no text or label, so screen readers cannot say where it goes.

No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.

The homepage links to 41 pages on pastelescid.com and 7 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.

There is no https://pastelescid.com/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://pastelescid.com/por-ocasion and https://pastelescid.com/por-ingredientes all use the title “Pastelería en Cancún”, and 1 other title repeat too. Search engines can't tell which page to show for a search, so each competes with the others.

https://pastelescid.com/contactanos has no meta description, so Google writes the search snippet from whatever text it finds.

https://pastelescid.com/por-ocasion and https://pastelescid.com/por-ingredientes use the same meta description. A description written for each page earns more clicks.

https://pastelescid.com/por-ocasion, https://pastelescid.com/por-ingredientes and https://pastelescid.com/contactanos have no <h1> headline, so visitors and search engines get no clear main topic.

https://pastelescid.com/contactanos has 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://pastelescid.com/pasteles-de-baby-showers-en-cancun took over 3 s to send its HTML from our server.

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

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.

A local customer looking to call finds no phone number on the homepage. Add one, ideally as a tap-to-call link.

Social proof on the homepage: 31 testimonial or review blocks. 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 phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.

There is no form on the homepage, so every lead has to click through to another page first.

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

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