travesiasmedia.com website review

14 images could be 16.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 24.9 s faster on a phone.

About 471 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.0 s faster on a phone.

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

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

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

8 third-party services load with your homepage (Google Tag Manager, Google/Doubleclick Ads and Google Maps and others), adding 1.0 MB and 592 ms of main-thread time.

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

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

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

Google/Doubleclick Ads costs a phone 176 ms of main-thread work and 311 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.

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

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

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.

Your largest element takes 30.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “SIAR 2026: veinte años de alta relojería en México”.

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

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

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

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

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

Your homepage downloads 17.8 MB in 81 requests on a phone: images 16.6 MB (29), scripts 1.1 MB (29) and other files 45 KiB (13). Under 2 MB keeps phones on slow connections fast.

8 images weigh 10.8 MB together. On a phone connection a single image that size takes seconds.

5 images are downloaded at several times the size a phone draws them, for example 201026-SIAR-057.jpg at 5,054 px wide, shown at 350 px. Resized copies would save about 3.5 MB.

8 images (7.4 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.

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

All page content should be contained by landmarks: 43 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.

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

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

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

Your meta description is only 26 characters: “Inspiración para viajeros.”. 70 to 160 characters is enough to sell the click.

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

The homepage links to 344 pages on travesiasmedia.com and 18 external pages.

There is no https://www.travesiasdigital.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.

Your homepage links to https://www.travesiasdigital.com/noticias, which answers with an error. Visitors hit a dead end and search engines drop it.

https://www.travesiasdigital.com/el-mundo, https://www.travesiasdigital.com/guias-de-viaje, https://www.travesiasdigital.com/inspiracion, https://www.travesiasdigital.com/perpetual-planet, https://www.travesiasdigital.com/newsletter and https://www.travesiasdigital.com/seccion/destinos/mexico/norte/baja-california/ensenada have no meta description, so Google writes the search snippet from whatever text it finds.

https://www.travesiasdigital.com/mexico, https://www.travesiasdigital.com/el-mundo, https://www.travesiasdigital.com/perpetual-planet and https://www.travesiasdigital.com/newsletter have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.travesiasdigital.com/newsletter 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://www.travesiasdigital.com/inspiracion, https://www.travesiasdigital.com/seccion/destinos/mexico/sureste/campeche, https://www.travesiasdigital.com/seccion/destinos/mexico/occidente/jalisco/careyes, https://www.travesiasdigital.com/seccion/destinos/mexico/centro-y-golfo/ciudad-de-mexico, https://www.travesiasdigital.com/seccion/destinos/mexico/centro-y-golfo/morelos/cuernavaca and https://www.travesiasdigital.com/seccion/destinos/mexico/norte/baja-california/ensenada took over 3 s to send their HTML from our server.

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

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

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

1 image is displayed at the wrong aspect ratio, so it looks stretched or squashed.

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

Before a visitor clicks anything, the page loads Comscore, 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 18 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 21 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.