iqtsystems.com website review

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

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

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

4 third-party services load with your homepage (Google Tag Manager, JSDelivr CDN and Google Fonts and others), adding 6.8 MB and 81 ms of main-thread time.

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

About 100 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 470 ms faster on a phone.

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

4 images could be 79 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 300 ms faster on a phone.

About 38 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 79 ms. During a long task the page ignores taps.

8 KiB could be saved by minifying CSS.

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.

Your largest element takes 5.2 s to render on a phone. Google's threshold for “good” is 2.5 s. The largest element is the image “Desarrollo de Software”.

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

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

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

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

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

Your homepage downloads 7.5 MB in 53 requests on a phone: images 6.8 MB (10), scripts 289 KiB (22) and fonts 271 KiB (7). Under 2 MB keeps phones on slow connections fast.

3 images are downloaded at several times the size a phone draws them, for example DALL·E2025-01-2317.49.30-Avisuallystrikingdigitalillustratio at 1,792 px wide, shown at 330 px. Resized copies would save about 4.5 MB.

3 images (6.7 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.

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

iq-logo-blue.webp is on the first screen but marked loading="lazy", so the browser waits before fetching it and the page looks finished later. Load it eagerly (and give it fetchpriority="high" if it is the main image).

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

1 button has no accessible name, so screen readers announce just “button”.

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

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

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

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

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

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

Your title is only 22 characters: “Desarrollo de Software”. 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.

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

Your meta description is 247 characters; Google truncates after about 160, so the end of your pitch is cut.

The homepage links to 59 pages on iqtsystems.com and 8 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://iqtsystems.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://iqtsystems.com/contacto, https://iqtsystems.com/banca-servicios-financieros, https://iqtsystems.com/logistica-y-transporte, https://iqtsystems.com/tercer-sector and https://iqtsystems.com/retail-e-commerce and 2 others all use the title “Desarrollo de Software”. Search engines can't tell which page to show for a search, so each competes with the others.

https://iqtsystems.com/contacto, https://iqtsystems.com/banca-servicios-financieros, https://iqtsystems.com/logistica-y-transporte, https://iqtsystems.com/tercer-sector, https://iqtsystems.com/retail-e-commerce and https://iqtsystems.com/blog and 1 other use the same meta description. A description written for each page earns more clicks.

https://iqtsystems.com/lang/en has no <h1> headline, so visitors and search engines get no clear main topic.

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

2 errors were logged to the browser console while the page loaded, for example “Loading the script 'https://www.google.com/recaptcha/enterprise.js?render=6Lf0b74qAAAAAEP8M4haHmIcLMJ_ZzCnMP8AyVqx' vio…”.

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

Chrome logged issues while loading the page (“Content security policy”).

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

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

The homepage has only about 218 words of visible text; thin pages give Google and first-time buyers little to go on.

No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.

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