Website review, no card needed
aspyprevencion.com website review
Visit site (opens in a new tab)Reviewed 28 October 202640 issues · 86 checks
This review found 40 issues worth fixing on aspyprevencion.com, 22 of them high impact, across 86 checks. The most urgent: use efficient cache lifetimes. 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
69DClosest competitors among reviewed websites
Compare side by sideShow as table
| Date | Real-visitor load time (LCP) |
|---|---|
| May 9, 2026 | 5.5 s |
| May 16, 2026 | 5.5 s |
| May 23, 2026 | 5.5 s |
| May 30, 2026 | 5.6 s |
| Jun 6, 2026 | 5.7 s |
| Jun 13, 2026 | 5.7 s |
| Jun 20, 2026 | 5.8 s |
| Jun 27, 2026 | 5.8 s |
| Jul 4, 2026 | 5.8 s |
| Jul 11, 2026 | 5.7 s |
| Jul 18, 2026 | 5.6 s |
| Jul 25, 2026 | 5.6 s |
| Aug 1, 2026 | 5.6 s |
| Aug 8, 2026 | 5.6 s |
| Aug 15, 2026 | 5.7 s |
| Aug 22, 2026 | 5.8 s |
| Aug 29, 2026 | 5.9 s |
| Sep 5, 2026 | 5.9 s |
| Sep 12, 2026 | 5.9 s |
| Sep 19, 2026 | 5.8 s |
| Sep 26, 2026 | 5.8 s |
| Oct 3, 2026 | 5.8 s |
| Oct 10, 2026 | 5.8 s |
| Oct 17, 2026 | 5.8 s |
| Oct 24, 2026 | 5.8 s |
Show as table
| Date | Real-visitor tap response (INP) |
|---|---|
| May 9, 2026 | 191 ms |
| May 16, 2026 | 190 ms |
| May 23, 2026 | 187 ms |
| May 30, 2026 | 187 ms |
| Jun 6, 2026 | 188 ms |
| Jun 13, 2026 | 189 ms |
| Jun 20, 2026 | 191 ms |
| Jun 27, 2026 | 194 ms |
| Jul 4, 2026 | 196 ms |
| Jul 11, 2026 | 197 ms |
| Jul 18, 2026 | 195 ms |
| Jul 25, 2026 | 193 ms |
| Aug 1, 2026 | 193 ms |
| Aug 8, 2026 | 193 ms |
| Aug 15, 2026 | 194 ms |
| Aug 22, 2026 | 194 ms |
| Aug 29, 2026 | 193 ms |
| Sep 5, 2026 | 189 ms |
| Sep 12, 2026 | 189 ms |
| Sep 19, 2026 | 187 ms |
| Sep 26, 2026 | 187 ms |
| Oct 3, 2026 | 188 ms |
| Oct 10, 2026 | 187 ms |
| Oct 17, 2026 | 188 ms |
| Oct 24, 2026 | 188 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
1.4 s
2.8 s
4.2 s
5.6 s
7.0 s
8.4 s
9.9 s
11.3 s
Speed
Use efficient cache lifetimes
3.1 s · 1.8 MB99 files are served with short cache lifetimes, so returning visitors download them again (1.8 MB).
Render-blocking requests
4.3 s52 files block the first paint until they finish downloading. Deferring or inlining them could save about 4.3 s.
Reduce unused JavaScript
1.6 s · 688 KiBAbout 688 KiB of JavaScript is downloaded but never used on this page. Google estimates it would make the page about 1.6 s faster on a phone.
Font display
1.1 sWeb fonts hide text while they load. Setting font-display: swap shows text immediately (about 1.1 s).
Mobile performance score: 39
39/100Your mobile performance score is 39 (desktop: 64). Under 50 is Google's “poor” band: many phone visitors leave before the page is usable.
Main-thread work: 4.2 s
A phone's processor spends 4.2 s on main-thread work while loading, 2.2 s of it running JavaScript. Above 2 s, taps and scrolls feel sluggish.
Improve image delivery
900 ms · 557 KiB13 images could be 557 KiB smaller with modern formats (WebP or AVIF) and sizes that fit a phone screen. Google estimates it would make the page about 900 ms faster on a phone.
7 third-party services on the page
7 third-party services load with your homepage (Google CDN, Google Tag Manager and Google Maps and others), adding 1.1 MB and 1.0 s of main-thread time.
Google CDN adds 589 ms
589 msGoogle CDN costs a phone 589 ms of main-thread work and 734 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.
Reduce unused CSS
300 ms · 69 KiBAbout 69 KiB of CSS is downloaded but never applied on this page. Google estimates it would make the page about 300 ms faster on a phone.
Google Tag Manager adds 250 ms
250 msGoogle Tag Manager costs a phone 250 ms of main-thread work and 177 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.
18 long tasks on the main thread
18 long tasks block the main thread while loading, the longest for 221 ms. During a long task the page ignores taps.
Minify JavaScript
150 ms · 23 KiB23 KiB could be saved by minifying JavaScript.
Phones get a much slower page than desktops
Desktop scores 64 but mobile only 39. A gap that wide usually means heavy scripts and images that hit phones hardest.
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.
Legacy JavaScript
4 KiBPolyfills for old browsers add 4 KiB JavaScript that modern phones do not need.
1 checks passed
Server response: 118 ms
118 msYour server sent the HTML in 118 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: 4.3 s
4.3 sReal visitors wait 4.3 s for the largest content to appear (75th percentile). Good is under 2.5 s.
Real-user FCP: 3.9 s
3.9 sReal visitors see the first content after 3.9 s (75th percentile). Good is under 1.8 s.
Real-user TTFB: 2.1 s
2.1 sReal visitors wait 2.1 s for your server to start answering (75th percentile). Good is under 800 ms.
Speed Index: 16.0 s
16.0 sVisually, the page fills in at 16.0 s (Speed Index). Good is under 3.4 s.
Largest Contentful Paint: 9.3 s
9.3 sYour largest element takes 9.3 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 (7.5 s).
Time to Interactive: 18.5 s
18.5 sThe page becomes fully interactive after 18.5 s. Good is under 3.8 s.
First Contentful Paint: 4.9 s
4.9 sThe first text or image appears after 4.9 s on a phone. Good is under 1.8 s.
Total Blocking Time: 697 ms
697 msScripts block taps and scrolling for 697 ms in total while the page loads. Good is under 200 ms.
Tap response (INP) held steady for real visitors
-1%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' tap response (inp) went from 191 ms to 188 ms at the 75th percentile (Chrome UX Report (opens in a new tab) history).
Largest content (LCP) held steady for real visitors
+6%Over the last 25 four-week periods to 2026-10-24, real Chrome visitors' largest content (lcp) went from 5.5 s to 5.8 s at the 75th percentile (Chrome UX Report (opens in a new tab) history).
3 checks passed
Real-user INP: 146 ms
146 msReal visitors wait 146 ms for the page to respond to a tap (75th percentile). Good is under 200 ms.
Real-user CLS: 0.03
0.03For real visitors the layout shifts by 0.03 (75th percentile). Good is under 0.1.
Cumulative Layout Shift: 0.04
0.04The layout barely moves while loading (CLS 0.04, good is under 0.1).
Images and page weight
Page weight: 3.2 MB in 119 requests
3.2 MBYour homepage downloads 3.2 MB in 119 requests on a phone: scripts 1.5 MB (49), images 888 KiB (15) and other files 359 KiB (7). Under 2 MB keeps phones on slow connections fast.
5 images in older formats
5 images (174 KiB) 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 (134 KiB) download before anyone scrolls to them. Adding loading="lazy" lets the first screen load first.
About 0.9 g of CO₂ per visit
0.91 gBy the Sustainable Web Design model, a visit to your homepage emits about 0.91 g of CO₂e: 108.7 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
13 text elements with low contrast
13 text elements don't have enough contrast against the background to read easily, especially outdoors on a phone.
2 tap targets too small
2 tap targets are too small or too close together to hit reliably with a finger.
lang attribute must have a valid value (1 element)
lang attribute must have a valid value: 1 element on the page fails this check, rated serious by axe-core.
All page content should be contained by landmarks (2 elements)
All page content should be contained by landmarks: 2 elements on the page fail this check, rated moderate by axe-core.
Zoom is disabled
The viewport tag blocks pinch-zoom, which low-vision visitors rely on.
2 links without text
2 visible links have no text or label, so screen readers cannot say where they go.
1 form field without a label
1 form field has no label, so screen readers announce an empty box and autofill guesses.
Headings skip levels
Headings skip levels (h2 → h5), which makes the page harder to scan with a screen reader.
2 checks passed
Every image has alt text
All 8 images in the HTML carry an alt attribute.
47 automated accessibility rules passed
axe-core 4.13.0, the open-source engine behind most accessibility testing tools, ran 54 WCAG 2.2 A/AA and best-practice rules on the phone render: 47 passed and 7 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 social preview image
No Open Graph image, so links shared on LinkedIn, Slack or Facebook show no preview picture.
5 links with vague text
5 links use generic text like “click here” or “learn more”, which tells Google nothing about the page behind them.
121 internal links, 30 external
The homepage links to 121 pages on aspyprevencion.com and 30 external pages.
6 checks passed
Meta description: 144 characters
Your meta description is 144 characters: “Servicio de prevención ajeno acreditado a nivel nacional. Damos la mejor respuesta a las necesidades de las empresas en…”.
Title: 50 characters
Your title is a healthy 50 characters: “ASPY | Servicio de Prevención de Riesgos Laborales”.
Canonical URL set
The canonical URL is https://www.aspyprevencion.com/.
Structured data in place
Structured data found: BreadcrumbList, Organization, WebPage and WebSite.
robots.txt in place
robots.txt is in place.
XML sitemap found
Your XML sitemap is reachable at https://www.aspyprevencion.com/sitemap.xml.
AI search readiness
Organization data is thin (3 of 6 facts)
Your Organization JSON-LD is missing logo, sameAs (social profiles) and contact details. These are the facts AI assistants use to describe a business and to tell it apart from others with a similar name.
3 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 (3,065 words), so crawlers that don't run JavaScript still read it.
llms.txt published
The site publishes https://www.aspyprevencion.com/llms.txt (146 KiB, 792 links), a plain-text guide to the site for AI tools.
Other pages
4 pages without a meta description
https://www.aspyprevencion.com/project-type/prevencion-integral, https://www.aspyprevencion.com/productos/prlautonom, https://www.aspyprevencion.com/productos/hogar and https://www.aspyprevencion.com/project-type/higiene-industrial have no meta description, so Google writes the search snippet from whatever text it finds.
10 pages without an H1
https://www.aspyprevencion.com/presupuesto, https://www.aspyprevencion.com/contacto, https://www.aspyprevencion.com/acreditaciones, https://www.aspyprevencion.com/condiciones-generales, https://www.aspyprevencion.com/productos and https://www.aspyprevencion.com/productos/contrato-integral-2-2 and 4 others have no <h1> headline, so visitors and search engines get no clear main topic.
12 pages slow to respond
https://www.aspyprevencion.com/contacto, https://www.aspyprevencion.com/trabaja-con-nosotros, https://www.aspyprevencion.com/quienes-somos, https://www.aspyprevencion.com/acreditaciones, https://www.aspyprevencion.com/mision-vision-y-valores and https://www.aspyprevencion.com/condiciones-generales and 6 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 57 found) and read each the way a search engine does.
5 checks passed
Linked pages load
All 15 pages we checked loaded without an error.
Canonical URLs point to themselves
No page we checked hands its ranking to a different URL.
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 15 pages that loaded have a <title>.
Best practices
41 small tap targets
41 of 92 tappable elements near the top of the page are smaller than 24 px, hard to hit with a thumb.
2 JavaScript errors while loading
2 errors were logged to the browser console while the page loaded, for example “Failed to load resource: net::ERR_FAILED”.
Missing source maps
Large scripts ship without source maps.
1 checks passed
Mobile viewport set
The page declares a mobile viewport.
Content and conversion
No call to action on the first screen
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 calls to action
We found no call-to-action buttons or links (such as “Book a demo” or “Get a quote”) anywhere on the homepage.
No social proof
No testimonials, customer logos, ratings or customer counts on the homepage: nothing tells a new visitor that others already trust you.
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.
About 463 words of copy
The homepage carries about 463 words of visible text.
3 checks passed
1 short form
A short form (1 field at most) is right on the homepage.
Analytics in place
Analytics detected: Google Analytics.
Direct contact links
Visitors can reach you directly: 2 phone links and 0 email links.
Privacy and tracking
2 trackers load before any consent
2Before a visitor clicks anything, the page loads 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.
5 cookies set on arrival
5Opening the homepage sets 5 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.
8 other companies contacted
Loading the homepage contacts 8 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 aspyprevencion.com, because details like these could help someone attack a site. Every review keeps them private, whatever they found.
Upkeep, stack and company
Stack
- Hosting
- Hetzner
Upkeep, stack, hiring and company data from programmable.info
Go beyond the website
What your $25 Growth Playbook adds
This review found 40 issues on aspyprevencion.com, including 20 speed issues, 3 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.