Website review, no card needed
applusidiada.com website review
Visit site (opens in a new tab)Reviewed 24 October 202644 issues · 86 checks
This review found 44 issues worth fixing on applusidiada.com, 15 of them high impact, across 86 checks. The most urgent: render-blocking requests. Your full playbook turns these into prioritised fixes alongside reviews, competitors and channels.
- Homepage
- Phone render
- Links and pages
- Google PageSpeed
Google PageSpeed Insights (opens in a new tab), mobile
Site score
75CClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 2, 2026 | 4.1 s |
| May 9, 2026 | 3.9 s |
| May 16, 2026 | 4.1 s |
| May 23, 2026 | 4.0 s |
| May 30, 2026 | 4.2 s |
| Jun 6, 2026 | 4.2 s |
| Jun 13, 2026 | 3.9 s |
| Jun 20, 2026 | 3.9 s |
| Jun 27, 2026 | 3.9 s |
| Jul 4, 2026 | 3.9 s |
| Jul 11, 2026 | 4.0 s |
| Jul 18, 2026 | 4.1 s |
| Jul 25, 2026 | 4.1 s |
| Aug 1, 2026 | 3.9 s |
| Aug 8, 2026 | 3.7 s |
| Aug 15, 2026 | 3.7 s |
| Aug 22, 2026 | 3.6 s |
| Aug 29, 2026 | 3.5 s |
| Sep 5, 2026 | 3.5 s |
| Sep 12, 2026 | 3.4 s |
| Sep 19, 2026 | 3.4 s |
| Sep 26, 2026 | 3.5 s |
| Oct 3, 2026 | 3.6 s |
| Oct 10, 2026 | 3.9 s |
| Oct 17, 2026 | 4.0 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 2, 2026 | 111 ms |
| May 9, 2026 | 111 ms |
| May 16, 2026 | 111 ms |
| May 23, 2026 | 108 ms |
| May 30, 2026 | 109 ms |
| Jun 6, 2026 | 108 ms |
| Jun 13, 2026 | 111 ms |
| Jun 20, 2026 | 110 ms |
| Jun 27, 2026 | 111 ms |
| Jul 4, 2026 | 111 ms |
| Jul 11, 2026 | 110 ms |
| Jul 18, 2026 | 114 ms |
| Jul 25, 2026 | 124 ms |
| Aug 1, 2026 | 128 ms |
| Aug 8, 2026 | 130 ms |
| Aug 15, 2026 | 131 ms |
| Aug 22, 2026 | 124 ms |
| Aug 29, 2026 | 123 ms |
| Sep 5, 2026 | 126 ms |
| Sep 12, 2026 | 127 ms |
| Sep 19, 2026 | 127 ms |
| Sep 26, 2026 | 130 ms |
| Oct 3, 2026 | 132 ms |
| Oct 10, 2026 | 132 ms |
| Oct 17, 2026 | 133 ms |
Chrome UX Report (opens in a new tab): real Chrome visitors over rolling 28-day periods.
One score from every part of this review. How it works
How it loaded on a phone
0.8 s
1.6 s
2.4 s
3.1 s
3.9 s
4.7 s
5.5 s
6.3 s
Speed
Render-blocking requests
2.8 s24 files block the first paint until they finish downloading. Deferring or inlining them could save about 2.8 s.
Reduce unused CSS
1.1 s · 204 KiBAbout 204 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 1.1 s faster on a phone.
Mobile performance score: 49
49/100Your mobile performance score is 49 (desktop: 70). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Improve image delivery
150 ms · 1.1 MB21 images could be 1.1 MB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 150 ms faster on a phone.
Reduce unused JavaScript
750 ms · 140 KiBAbout 140 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 750 ms faster on a phone.
4 third-party services on the page
4 third-party services load with your homepage (Google Tag Manager, Google Analytics and metricool.com and others), adding 398 KiB and 554 ms of main-thread time.
Google Tag Manager adds 532 ms
532 msGoogle Tag Manager costs a phone 532 ms of main-thread work and 368 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.
6 long tasks on the main thread
6 long tasks block the main thread while loading, the longest for 356 ms. During a long task the page ignores taps.
Minify CSS
300 ms · 34 KiB34 KiB could be saved by minifying CSS.
Use efficient cache lifetimes
150 ms · 17 KiB2 files are served with short cache lifetimes, so returning visitors download them again (17 KiB).
Minify JavaScript
150 ms · 13 KiB13 KiB could be saved by minifying JavaScript.
Legacy JavaScript
16 KiBPolyfills for old browsers add 16 KiB JavaScript that modern phones do not need.
Chained critical requests
Critical files load one after another instead of in parallel (3 chains). Preconnecting to key origins and preloading the hero image shortens the chain.
Forced reflow
Scripts make the browser recalculate the layout repeatedly while the page loads, which wastes processor time on phones.
2 checks passed
Main-thread work: 1.6 s
A phone's processor spends 1.6 s on main-thread work while loading, 802 ms of it running JavaScript. That is comfortably low.
Server response: 237 ms
237 msYour server sent the HTML in 237 ms, well inside Google's 600 ms guideline.
Core Web Vitals
Fails Core Web Vitals for real visitors
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-user LCP: 5.0 s
5.0 sReal visitors wait 5.0 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.7 s
3.7 sReal visitors see the first content after 3.7 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 3.4 s
3.4 sReal visitors wait 3.4 s for your server to start answering (75th percentile). Good is under 800 ms.
Largest Contentful Paint: 11.2 s
11.2 sYour largest element takes 11.2 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 resource load delay (5.9 s).
Speed Index: 10.3 s
10.3 sVisually, the page fills in at 10.3 s (Speed Index). Good is under 3.4 s.
Time to Interactive: 11.2 s
11.2 sThe page becomes fully interactive after 11.2 s. Good is under 3.8 s.
First Contentful Paint: 2.8 s
2.8 sThe first text or image appears after 2.8 s on a phone. Good is under 1.8 s.
Total Blocking Time: 464 ms
464 msScripts block taps and scrolling for 464 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) got 19% slower for real visitors
+19%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' tap response (inp) went from 111 ms to 133 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
-2%Over the last 25 four-week periods to 2026-10-17, real Chrome visitors' largest content (lcp) went from 4.1 s to 4.0 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 126 ms
126 msReal visitors wait 126 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.01
0.01For real visitors the layout shifts by 0.01 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.062
0.062The layout barely moves while loading (CLS 0.062, good is under 0.1).
Images and page weight
4 images over 500 KB
4 images weigh 2.4 MB together. On a phone connection a single image that size takes seconds.
Page weight: 3.2 MB in 89 requests
3.2 MBYour homepage downloads 3.2 MB in 89 requests on a phone: images 2.3 MB (47), scripts 571 KiB (26) and stylesheets 247 KiB (10). Under 2 MB keeps phones on slow connections fast.
6 images in older formats
6 images (2.5 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.
4 images below the first screen load straight away
4 images further down the page (2.4 MB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.90 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.90 g of CO₂e: 108.5 kg a year at 10,000 visits a month. It scales with page weight, so every byte cut lowers it.
1 checks passed
Images are sized for phones
No image is downloaded at more than three times the size it is drawn on a phone.
Accessibility
1 button without a name
1 button has no accessible name, so screen readers announce just “button”.
14 text elements with low contrast
14 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
8 tap targets too small
8 tap targets are too small or too close together to hit reliably with a finger.
All page content should be contained by landmarks (26 elements)
All page content should be contained by landmarks: 26 elements on the page fail this check, rated moderate by axe-core.
No main landmark
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)
Page should contain a level-one heading: 1 element on the page fails this check, rated moderate by axe-core.
11 links without text
11 visible links have no text or label, so screen readers cannot say where they go.
Headings should not be empty (1 element)
Headings should not be empty: 1 element on the page fails this check, rated minor by axe-core.
2 checks passed
Every image has alt text
All 25 images in the HTML carry an alt attribute.
32 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 40 WCAG 2.2 A/AA and best-practice rules on the phone render: 32 passed and 8 failed. 2 mores need a person to judge. Automated rules catch about a third of accessibility problems; the rest need manual testing.
SEO
No H1 headline
There is no <h1>, so neither visitors nor Google get a clear main headline.
No structured data
No structured data (JSON-LD), so Google can't show rich results such as your logo, ratings or FAQs.
No social preview image
No Open Graph image (also missing: og:description), so links shared on LinkedIn, Slack or Facebook show no preview picture.
No XML sitemap
No XML sitemap at https://www.applusidiada.com/sitemap.xml, so Google discovers your pages only by following links.
6 links crawlers can't follow
6 links have no real href, so search engines can't follow them.
103 internal links, 24 external
The homepage links to 103 pages on applusidiada.com and 24 external pages.
4 checks passed
Meta description: 152 characters
Your meta description is 152 characters: “Applus+ IDIADA is a leading company specialized in providing design, engineering, testing and homologation services to …”.
Title: 62 characters
Your title is a healthy 62 characters: “IDIADA: Automotive design, engineering, testing & homologation”.
Canonical URL set
The canonical URL is https://www.applusidiada.com/global/en/.
robots.txt in place
robots.txt is in place.
AI search readiness
No Organization structured data
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.
No llms.txt
There is no https://www.applusidiada.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.
2 checks passed
AI answer engines may read the site
Your robots.txt lets the crawlers behind ChatGPT search, Claude and Perplexity read the site and cite it in answers.
Text is in the HTML
Your server sends the page's text in the HTML (606 words), so crawlers that don't run JavaScript still read it.
Other pages
1 page without an H1
https://www.applusidiada.com/global/es has no <h1> headline, so visitors and search engines get no clear main topic.
10 pages slow to respond
https://www.applusidiada.com/global/es, https://www.applusidiada.com/global/en/what-we-do/services/automotive-body-design, https://www.applusidiada.com/global/en/what-we-do/services/body-performance-engineering, https://www.applusidiada.com/global/en/what-we-do/services/durability--reliability, https://www.applusidiada.com/global/en/what-we-do/services/electronics and https://www.applusidiada.com/global/en/what-we-do/services/nvh and 4 others took over 3 s to send their HTML from our server.
15 internal pages checked
We fetched 15 pages linked from your homepage (of 49 found) and read each the way a search engine does.
6 checks passed
Linked pages load
13 pages of 15 loaded without an error (the rest turned automated requests away).
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
Every page has a meta description
All 13 pages that loaded have a meta description.
Titles are unique
Every page we checked has its own title.
No linked page is hidden from search
None of the pages we checked carries a noindex tag.
Every page has a title
All 13 pages that loaded have a <title>.
Best practices
19 small tap targets
19 of 50 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
1 JavaScript error while loading
1 error was logged to the browser console while the page loaded, for example “Executing inline event handler violates the following Content Security Policy directive 'script-src 'self' 'unsafe-eval…”.
3 distorted images
3 images are displayed at the wrong aspect ratio, so they look stretched or squashed.
Browser-reported issues
Chrome logged issues while loading the page (“Content security policy”).
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
Thin social proof
Social proof on the homepage: 1 testimonial or review block. Pairing it with named testimonials or customer logos makes it far more convincing.
No direct contact details
No phone number or email link on the homepage, so ready-to-buy visitors have one fewer way to reach you.
Only about 235 words
The homepage has only about 235 words of visible text; thin pages give Google and first-time buyers little to go on.
No risk reducer
No guarantee or risk reducer (money-back, free trial, no credit card) is mentioned, which is often what tips a hesitant visitor.
4 checks passed
Clear next step on the first screen
On a phone, the first screen shows a clear next step: “CONTACT US”.
3 calls to action
The homepage has 3 calls to action, for example “Contact”, “Contact us form” and “contact us”.
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Privacy and tracking
3 trackers load before any consent
3Before a visitor clicks anything, the page loads 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.
8 cookies set on arrival
8Opening the homepage sets 8 cookies (measured from a US location before any click).
No consent tool detected
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.
5 other companies contacted
Loading the homepage contacts 5 hosts run by other companies (fonts, scripts, analytics, ads), each of which sees the visitor's IP address.
Security, domain, email and software versions
The security, domain and email checks, software and plugin versions, and any app with a known security problem are visible only to people at applusidiada.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Framework
- Vue.js
- Analytics
- Google Analytics
Company
- Founded
- 1990
- Headquarters
- Santa Oliva
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 44 issues on applusidiada.com, including 18 speed issues, 5 SEO issues and 3 conversion gaps. That is the website alone. The full Growth Playbook pairs these findings with what your customers say in public reviews and communities and what your closest competitors do better, then turns everything into at least 20 prioritised ideas, each with the evidence behind it, a step-by-step playbook, a metric and an owner.
- 28 research agents read your site, reviews, competitors, communities and public filings
- Customer review mining (G2, Capterra, Trustpilot and more) and voice-of-pain analysis in your buyers’ own words
- Competitor intelligence with battlecards for your closest rivals
- Ideal customer profile, buyer segments and buying-stage funnel
- Ranked channels, outreach sequences and content angles
- Live Reddit threads where buyers ask for what you sell, with draft replies
- Earned media and PR openings
- At least 20 ideas with evidence, a step-by-step playbook, metric, owner, effort and impact, grouped into this week, this quarter, big bets and wildcards, plus a 30/60/90-day roadmap
- PDF, Markdown, CSV, Notion and Linear exports, and a shareable page your team can track progress on
- Refresh the playbook later to see what changed
14-day money-back guarantee: not happy for any reason, email us within 14 days and we refund in full.