360industrialpark.com website review

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

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

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

5 third-party services load with your homepage (Google Maps, googleapis.com and 360industrialparks.com and others), adding 22.6 MB and 83 ms of main-thread time.

360industrialparks.com costs a phone 0 ms of main-thread work and 18.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.

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

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

Amazon Web Services costs a phone 0 ms of main-thread work and 4.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.

Google Maps costs a phone 83 ms of main-thread work and 301 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 24 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 160 ms faster on a phone.

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

Polyfills for old browsers add 12 KiB JavaScript that modern phones do not need.

Your largest element takes 106.4 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the text “Your Industrial Real Estate Partner in Mexico”.

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

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

9 images 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 23.0 MB in 64 requests on a phone: images 22.0 MB (17), scripts 560 KiB (21) and other files 318 KiB (20). Under 2 MB keeps phones on slow connections fast.

5 images weigh 21.9 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 pmat_rev2_02_+1.jpg at 5,464 px wide, shown at 320 px. Resized copies would save about 19.8 MB.

7 images (21.9 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.

9 images further down the page (22.0 MB) 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 6.51 g of CO₂e: 781.3 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.

1 text element doesn't have enough contrast against the background to read easily, especially outdoors on a phone.

Interactive controls must not be nested: 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.

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

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

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

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

Your title is only 20 characters: “360 Industrial Parks”. 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.

Your meta description is only 45 characters: “Your Industrial Real Estate Partner in Mexico”. 70 to 160 characters is enough to sell the click.

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

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

There is no robots.txt at 360industrialpark.com/robots.txt, the first file search crawlers ask for.

1 link use generic text like “click here” or “learn more”, which tells Google nothing about the page behind it.

No twitter:card tag. X falls back to Open Graph, which is set, so this is minor.

The homepage links to 15 pages on 360industrialpark.com and 2 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://www.360industrialpark.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://www.360industrialpark.com/servicios, https://www.360industrialpark.com/sustentabilidad, https://www.360industrialpark.com/about, https://www.360industrialpark.com/reportes, https://www.360industrialpark.com/parques/648277a8adb0916bdf5914cc and https://www.360industrialpark.com/parques/64827945279552b8295fe01f and 1 other have no <h1> headline, so visitors and search engines get no clear main topic.

https://www.360industrialpark.com/servicios and https://www.360industrialpark.com/reportes have 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.360industrialpark.com/about, https://www.360industrialpark.com/parques/648277a8adb0916bdf5914cc and https://www.360industrialpark.com/parques/65b1ae3510282909bfa9d7d4 took over 3 s to send their HTML from our server.

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

2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.

On a phone, there is no call to action on the first screen: visitors have to scroll to find out what to do next.

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 phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

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