Tools & Wizards About Us
pelayonex.com screenshot

Report Summary

  • 24

    Performance

    Renders faster than
    43% of other websites

  • 72

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

pelayonex.com

Pelayo seguros, tu compañía aseguradora de máxima confianza

Page Load Speed

9.4 sec in total

First Response

1.8 sec

Resources Loaded

7 sec

Page Rendered

606 ms

pelayonex.com screenshot

About Website

Visit pelayonex.com now to see the best up-to-date Pelayo Nex content and also check out these interesting facts you probably never knew about pelayonex.com

Descubre la Diferencia Pelayo y contrata ahora tu seguro con las mejores condiciones. En Pelayo te ofrecemos seguros que se adaptan 100% a tus necesidades. Entra y descubre las mejores coberturas grac...

Visit pelayonex.com

Key Findings

We analyzed Pelayonex.com page load time and found that the first response time was 1.8 sec and then it took 7.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

pelayonex.com performance score

24

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value11.4 s

5/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.134

80/100

15%

TTI (Time to Interactive)

Value11.9 s

16/100

10%

Network Requests Diagram

www.pelayo.com

1780 ms

gtm.js

76 ms

mentions.css

235 ms

main.css

235 ms

aui.css

563 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pelayonex.com, 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2.3 sec) relates to the external source Pelayo.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 304.3 kB (19%)

Content Size

1.6 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pelayonex.com main page is 1.6 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 35% of websites need less resources to load. Images take 607.3 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 290.2 kB

  • Original 323.9 kB
  • After minification 272.1 kB
  • After compression 33.8 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 51.8 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 290.2 kB or 90% of the original size.

Image Optimization

-2%

Potential reduce by 11.4 kB

  • Original 607.3 kB
  • After minification 595.9 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Pelayo Nex images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 196 B

  • Original 514.4 kB
  • After minification 514.4 kB
  • After compression 514.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-2%

Potential reduce by 2.6 kB

  • Original 135.1 kB
  • After minification 134.6 kB
  • After compression 132.5 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Pelayonex.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 27 (36%)

Requests Now

74

After Optimization

47

  • Images
  • JavaScript
  • CSS

The browser has sent 74 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pelayo Nex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

www.pelayo.com

www.pelayo.com

1780 ms

gtm.js

gtm.js

76 ms

mentions.css

mentions.css

235 ms

main.css

main.css

235 ms

aui.css

aui.css

563 ms

main.css

main.css

422 ms

combo

combo

275 ms

js_loader_modules

js_loader_modules

433 ms

everything.jsp

everything.jsp

1031 ms

js_bundle_config

js_bundle_config

547 ms

combo

combo

511 ms

main.css

main.css

1001 ms

combo

combo

766 ms

combo

combo

769 ms

analytics.min.js

analytics.min.js

1183 ms

liferay-analytics-api.js

liferay-analytics-api.js

795 ms

liferay-analytics-processor.js

liferay-analytics-processor.js

1000 ms

combo

combo

905 ms

main.js

main.js

1066 ms

main_pelayo_vass.js

main_pelayo_vass.js

1188 ms

main_pelayo.js

main_pelayo.js

1754 ms

130 ms

377 ms

234 ms

235 ms

combo

combo

428 ms

combo

combo

237 ms

combo

combo

94 ms

combo

combo

490 ms

5e0ba6ec-8a3d-6c13-2736-2f62c467ce64

5e0ba6ec-8a3d-6c13-2736-2f62c467ce64

349 ms

layout_icon

layout_icon

349 ms

layout_icon

layout_icon

347 ms

layout_icon

layout_icon

429 ms

layout_icon

layout_icon

509 ms

layout_icon

layout_icon

583 ms

layout_icon

layout_icon

584 ms

layout_icon

layout_icon

596 ms

8e3c3aa2-cd11-00e6-9afd-e774bc89c070

8e3c3aa2-cd11-00e6-9afd-e774bc89c070

600 ms

layout_icon

layout_icon

666 ms

layout_icon

layout_icon

745 ms

layout_icon

layout_icon

821 ms

layout_icon

layout_icon

833 ms

layout_icon

layout_icon

846 ms

layout_icon

layout_icon

849 ms

layout_icon

layout_icon

901 ms

layout_icon

layout_icon

980 ms

layout_icon

layout_icon

1056 ms

layout_icon

layout_icon

1068 ms

13dbfbe1-736d-6a04-5cdf-43222fbe3926

13dbfbe1-736d-6a04-5cdf-43222fbe3926

1087 ms

a434dee6-baa4-152b-ac62-0ebce1d3454e

a434dee6-baa4-152b-ac62-0ebce1d3454e

1104 ms

79a66803-8ec8-48af-5c4c-a69e539357f6

79a66803-8ec8-48af-5c4c-a69e539357f6

1142 ms

0193655f-732f-0a57-321a-59ec0b2074d3

0193655f-732f-0a57-321a-59ec0b2074d3

1220 ms

b1b5e644-86d0-5610-5388-2301dab0b19e

b1b5e644-86d0-5610-5388-2301dab0b19e

1297 ms

cc184a86-bfa1-126c-9420-3a381b55ac85

cc184a86-bfa1-126c-9420-3a381b55ac85

1310 ms

1afc9483-e778-9304-fc68-156964097793

1afc9483-e778-9304-fc68-156964097793

1465 ms

a1d3fb32-d317-c654-3f1f-885bdde9e902

a1d3fb32-d317-c654-3f1f-885bdde9e902

1343 ms

6329ffaf-c94d-79ac-e776-dd949ec8aba3

6329ffaf-c94d-79ac-e776-dd949ec8aba3

1382 ms

51955dff-7766-4f38-b9ea-22aa33a32d07

51955dff-7766-4f38-b9ea-22aa33a32d07

1477 ms

b08d1781-d280-f01a-e37f-3f56f73db597

b08d1781-d280-f01a-e37f-3f56f73db597

1548 ms

fd46ded2-f1f9-b5d9-0424-cbb71a27b26b

fd46ded2-f1f9-b5d9-0424-cbb71a27b26b

1553 ms

ea21cf82-820a-9ac5-44f1-8fe2331a27ee

ea21cf82-820a-9ac5-44f1-8fe2331a27ee

1583 ms

03f6f91a-b632-3fc4-5471-be89bd07ca2f

03f6f91a-b632-3fc4-5471-be89bd07ca2f

1616 ms

icomoon.ttf

icomoon.ttf

1733 ms

1369 ms

b0471669-1820-aa28-30ba-1aab4c96bb8b

b0471669-1820-aa28-30ba-1aab4c96bb8b

1691 ms

7c87a27c-fee1-aa54-d8e6-5c8f73500c33

7c87a27c-fee1-aa54-d8e6-5c8f73500c33

1625 ms

e4bef4c3-aed7-071b-1603-b145d67c3a7d

e4bef4c3-aed7-071b-1603-b145d67c3a7d

1872 ms

ee4ed2f0-751e-0c53-9ae1-5adb28c7d01a

ee4ed2f0-751e-0c53-9ae1-5adb28c7d01a

1403 ms

mark.png

mark.png

1461 ms

f4a286ac-16eb-c850-ff66-5c38415a8e4d

f4a286ac-16eb-c850-ff66-5c38415a8e4d

1613 ms

10fa86b7-29cb-092d-4dd0-9e8788359cc4

10fa86b7-29cb-092d-4dd0-9e8788359cc4

1500 ms

iqnet-vector-logo-sello.png

iqnet-vector-logo-sello.png

1546 ms

Symantec_logo-sello.png

Symantec_logo-sello.png

1631 ms

9b81cb75-7c95-10b9-f3d9-fe96a2b88013

9b81cb75-7c95-10b9-f3d9-fe96a2b88013

2263 ms

left-chevron.svg

left-chevron.svg

1651 ms

right-chevron.svg

right-chevron.svg

1612 ms

combo

combo

682 ms

177 ms

combo

combo

93 ms

available_languages.jsp

available_languages.jsp

259 ms

265 ms

264 ms

combo

combo

271 ms

combo

combo

379 ms

Accessibility Review

pelayonex.com accessibility score

72

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-*] attributes do not have valid values

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

pelayonex.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pelayonex.com SEO score

79

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pelayonex.com can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Pelayonex.com main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

pelayonex.com

Open Graph description is not detected on the main page of Pelayo Nex. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: