sitrack.com website review

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

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

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

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

Your mobile performance score is 41. Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.

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

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

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

Hubspot costs a phone 422 ms of main-thread work and 723 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.

Polyfills for old browsers add 26 KiB JavaScript that modern phones do not need. Google estimates it would make the page about 300 ms faster on a phone.

15 long tasks block the main thread while loading, the longest for 222 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 1.8 s for your server to start answering (75th percentile). Good is under 800 ms.

Your largest element takes 18.1 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the element shown below. Most of its time is element render delay (18.3 s).

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

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

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

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

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

Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 2.0 s to 2.7 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

5 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-24, real Chrome visitors' tap response (inp) went from 158 ms to 180 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).

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

10 images (3.1 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.

10 images further down the page (3.1 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.

Your homepage downloads 2.4 MB in 164 requests on a phone: scripts 1.8 MB (49), images 371 KiB (69) and stylesheets 150 KiB (19). Under 2 MB keeps phones on slow connections fast.

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

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

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

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

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

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.

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

5 visible links have no text or label, so screen readers cannot say where they go.

1 form field has no label, so screen readers announce an empty box and autofill guesses.

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

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

Your meta description is only 27 characters: “Just another WordPress site”. 70 to 160 characters is enough to sell the click.

Structured data found (ImageObject, WebPage and WebSite) but with 1 problem, for example “ImageObject: url is not an absolute URL ("https://www.sitrack.com/portal/wp-content/uploads/banners/rastreo-stelital-intel…”.

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

The homepage links to 24 pages on sitrack.com and 30 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.sitrack.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.sitrack.com/portal/mobileye/es and https://www.sitrack.com/portal/mexico/es, which answer with an error. Visitors hit a dead end and search engines drop them.

https://www.sitrack.com/portal/quienes-somos and https://www.sitrack.com/portal/contacto are marked noindex but linked from your homepage. If they are meant to be found, remove the noindex.

https://www.sitrack.com/portal/quienes-somos, https://www.sitrack.com/portal/soluciones, https://www.sitrack.com/portal/contacto, https://www.sitrack.com/portal/en/home, https://www.sitrack.com/portal/politica-de-seguridad-de-la-informacion and https://www.sitrack.com/portal/politicas-de-calidad and 2 others use the same meta description. A description written for each page earns more clicks.

https://www.sitrack.com/portal/ican/es/index.html, https://www.sitrack.com/portal/politica-de-seguridad-de-la-informacion, https://www.sitrack.com/portal/politicas-de-calidad, https://www.sitrack.com/portal/politicas-de-privacidad-de-app and https://www.sitrack.com/portal/politica-privacidad-informacion have no <h1> headline, so visitors and search engines get no clear main topic.

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

2 images are displayed at the wrong aspect ratio, so they look stretched or squashed.

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

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.

Your phone number appears as text but isn't a tel: link, so phone visitors can't tap to call.

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

Before a visitor clicks anything, the page loads Google Ads, Google Analytics, Google Tag Manager, HubSpot and LinkedIn Insight and 1 more (measured from a US location before any click). A consent tool (HubSpot cookie banner) is installed; check it blocks these until visitors agree where the law requires it.

Opening the homepage sets 11 cookies, 1 of them by other companies (measured from a US location before any click).

Loading the homepage contacts 28 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.