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

pelayo.com Website Information

Daily Unique Visits: 2,241

Daily Page Views: 6,723

Income Per Day: $20

Estimated Value: $7,200

This website is located in Unknown Zone and is using following IP address no. See the complete list of popular websites hosted in Unknown Zone.

pelayo.com is registered under .COM top-level domain. Please check other sites in .COM zone.

Website pelayo.com is using the following name servers:

  • no

and is probably hosted by VODAFONE ESPANA S.A.U.. See the full list of other websites hosted by VODAFONE ESPANA S.A.U..

The highest website pelayo.com position in Alexa rank database was 14463 and the lowest rank position was 865790. Current position of pelayo.com in Alexa rank database is 479945.

Desktop speed score of pelayo.com (56/100) is better than the results of 30.56% of other sites and shows that the page desktop performance can be improved.

Mobile usability score of pelayo.com (100/100) is better than the results of 100% of other sites and means that the page is mobile-friendly.

Mobile speed score of pelayo.com (61/100) is better than the results of 57.04% of other sites and shows that the landing page performance on mobile devices is poor and can be improved.

Advertisement

pelayo.com Alexa Rank

The traffic rank is based on three months of aggregated historical traffic data from millions of Alexa Toolbar users and is a combined measure of page views and users.


pelayo.com whois

WHOIS gives you the ability to lookup any generic domains to find out the registered domain holder. WHOIS database are provided for information purposes only. It allows the public to check whether a specific domain name is still available or not and to obtain information related to the registration records of existing domain names.


Domain Name: PELAYO.COM
Registry Domain ID: 1545087_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.tucows.com
Registrar URL: http://www.tucows.com
Updated Date: 2022-06-17T22:06:29Z
Creation Date: 1997-05-27T04:00:00Z
Registry Expiry Date: 2032-05-26T04:00:00Z
Registrar: Tucows Domains Inc.
Registrar IANA ID: 69
Registrar Abuse Contact Email: domainabuse@tucows.com
Registrar Abuse Contact Phone: +1.4165350123
Domain Status: ok https://icann.org/epp#ok
Name Server: ARTEMIS.TTD.NET
Name Server: DNS01.ONO.COM
Name Server: PELDNS.PELAYO.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-10-19T00:55:41Z

pelayo.com server information

Servers Location

pelayo.com desktop page speed rank

Last tested: 2018-12-25


Desktop Speed Bad
56/100

pelayo.com Desktop Speed Test Quick Summary


priority - 41Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 398.7KiB (79% reduction).

Compressing http://www.pelayo.com/javascripts/oficinaInternet.js could save 91.3KiB (84% reduction).
Compressing http://www.pelayo.com/javascripts/jquery.qtip.js could save 66.7KiB (80% reduction).
Compressing http://www.pelayo.com/javascripts/howCost/extrasAccesories.js could save 49.9KiB (83% reduction).
Compressing http://www.pelayo.com/javascripts/jquery.js could save 36.6KiB (65% reduction).
Compressing http://www.pelayo.com/javascripts/misPolizasResultsAutos.js could save 23.3KiB (91% reduction).
Compressing http://www.pelayo.com/javascripts/howCost/modelSelection.js could save 23KiB (82% reduction).
Compressing http://www.pelayo.com/javascripts/jquery.validate.min.js could save 18KiB (72% reduction).
Compressing http://www.pelayo.com/javascripts/altaOfficina.js could save 16.8KiB (81% reduction).
Compressing http://www.pelayo.com/javascripts/pelayocom.js could save 13.4KiB (76% reduction).
Compressing http://www.pelayo.com/javascripts/declararAccidente.js could save 12.6KiB (84% reduction).
Compressing http://www.pelayo.com/javascripts/jquery.colorbox-min.js could save 11.4KiB (74% reduction).
Compressing http://www.pelayo.com/javascripts/jquery.jmap.min.js could save 9.8KiB (72% reduction).
Compressing http://www.pelayo.com/javascripts/jquery.thickbox.js could save 9.4KiB (69% reduction).
Compressing http://www.pelayo.com/javascripts/ultimoRecibo.js could save 5.2KiB (74% reduction).
Compressing http://www.pelayo.com/javascripts/reporting.js could save 2.8KiB (70% reduction).
Compressing http://www.pelayo.com/javascripts/jquery.equalHeights.js could save 2.5KiB (63% reduction).
Compressing http://www.pelayo.com/javascripts/presentarQueja.js could save 2.4KiB (69% reduction).
Compressing http://www.pelayo.com/javascripts/fecha.js could save 1.4KiB (65% reduction).
Compressing http://www.pelayo.com/javascripts/conductores.js could save 1.2KiB (64% reduction).
Compressing http://www.pelayo.com/javascripts/jquery.validate.messages_es.js could save 754B (59% reduction).
Compressing http://www.pelayo.com/javascripts/captureonclick.js could save 184B (52% reduction).

priority - 23Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://www.pelayo.com/MFTP/Images/fixed/tarjetas.gif (expiration not specified)
http://www.pelayo.com/MFTP/Images/fixed/telefonos/bg_tel_Gral21_home.gif (expiration not specified)
http://www.pelayo.com/MFTP/Images/fixed/verisign-logo.gif (expiration not specified)
http://www.pelayo.com/MFTP/Images/promos/ac/AC-csp.png (expiration not specified)
http://www.pelayo.com/MFTP/Images/promos/ac/AC-diferencia.png (expiration not specified)
http://www.pelayo.com/MFTP/Images/promos/ac/AC-oficina-internet.png (expiration not specified)
http://www.pelayo.com/MFTP/Images/promos/ac/AC-recupera-tu-presupuesto.png (expiration not specified)
http://www.pelayo.com/MFTP/Images/promos/ac/AC-social-media2.png (expiration not specified)
http://www.pelayo.com/MFTP/Images/promos/home/home_diferencia1.png (expiration not specified)
http://www.pelayo.com/images/aspa-faldon-com.png (expiration not specified)
http://www.pelayo.com/images/bg_footer.png (expiration not specified)
http://www.pelayo.com/images/bg_main_menu.png (expiration not specified)
http://www.pelayo.com/images/bg_phone_footer.gif (expiration not specified)
http://www.pelayo.com/images/controls.png (expiration not specified)
http://www.pelayo.com/images/footer_bullet.gif (expiration not specified)
http://www.pelayo.com/images/loading.gif (expiration not specified)
http://www.pelayo.com/images/pelayocom.gif (expiration not specified)
http://www.pelayo.com/javascripts/altaOfficina.js (expiration not specified)
http://www.pelayo.com/javascripts/captureonclick.js (expiration not specified)
http://www.pelayo.com/javascripts/conductores.js (expiration not specified)
http://www.pelayo.com/javascripts/declararAccidente.js (expiration not specified)
http://www.pelayo.com/javascripts/fecha.js (expiration not specified)
http://www.pelayo.com/javascripts/howCost/extrasAccesories.js (expiration not specified)
http://www.pelayo.com/javascripts/howCost/modelSelection.js (expiration not specified)
http://www.pelayo.com/javascripts/jquery.colorbox-min.js (expiration not specified)
http://www.pelayo.com/javascripts/jquery.equalHeights.js (expiration not specified)
http://www.pelayo.com/javascripts/jquery.jmap.min.js (expiration not specified)
http://www.pelayo.com/javascripts/jquery.js (expiration not specified)
http://www.pelayo.com/javascripts/jquery.qtip.js (expiration not specified)
http://www.pelayo.com/javascripts/jquery.thickbox.js (expiration not specified)
http://www.pelayo.com/javascripts/jquery.validate.messages_es.js (expiration not specified)
http://www.pelayo.com/javascripts/jquery.validate.min.js (expiration not specified)
http://www.pelayo.com/javascripts/misPolizasResultsAutos.js (expiration not specified)
http://www.pelayo.com/javascripts/oficinaInternet.js (expiration not specified)
http://www.pelayo.com/javascripts/pelayocom.js (expiration not specified)
http://www.pelayo.com/javascripts/presentarQueja.js (expiration not specified)
http://www.pelayo.com/javascripts/reporting.js (expiration not specified)
http://www.pelayo.com/javascripts/ultimoRecibo.js (expiration not specified)
http://www.pelayo.com/stylesheets/colorbox.css (expiration not specified)
http://www.pelayo.com/stylesheets/pelayocom.css (expiration not specified)
http://www.pelayo.com/stylesheets/pelayocom_adds.css (expiration not specified)
http://www.pelayo.com/stylesheets/pelayocom_chrome.css (expiration not specified)
http://www.pelayo.com/stylesheets/pelayocom_print.css (expiration not specified)
http://www.googletagmanager.com/gtm.js?id=GTM-TWR7G4 (15 minutes)
http://c1.rfihub.net/js/tc.min.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 15Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 147.6KiB (37% reduction).

Minifying http://www.pelayo.com/javascripts/jquery.qtip.js could save 38.1KiB (46% reduction).
Minifying http://www.pelayo.com/javascripts/oficinaInternet.js could save 33.4KiB (32% reduction).
Minifying http://www.pelayo.com/javascripts/howCost/extrasAccesories.js could save 20.3KiB (35% reduction).
Minifying http://www.pelayo.com/javascripts/misPolizasResultsAutos.js could save 13.2KiB (51% reduction).
Minifying http://www.pelayo.com/javascripts/howCost/modelSelection.js could save 8.1KiB (29% reduction).
Minifying http://www.pelayo.com/javascripts/pelayocom.js could save 6.8KiB (39% reduction).
Minifying http://www.pelayo.com/javascripts/jquery.colorbox-min.js could save 6.5KiB (43% reduction).
Minifying http://www.pelayo.com/javascripts/altaOfficina.js could save 6KiB (30% reduction).
Minifying http://www.pelayo.com/javascripts/jquery.thickbox.js could save 4.6KiB (35% reduction).
Minifying http://www.pelayo.com/javascripts/jquery.equalHeights.js could save 2.7KiB (66% reduction).
Minifying http://www.pelayo.com/javascripts/declararAccidente.js could save 2.4KiB (17% reduction).
Minifying http://www.pelayo.com/javascripts/ultimoRecibo.js could save 1.7KiB (25% reduction).
Minifying http://www.pelayo.com/javascripts/reporting.js could save 1.2KiB (31% reduction).
Minifying http://www.pelayo.com/javascripts/fecha.js could save 884B (41% reduction).
Minifying http://www.pelayo.com/javascripts/presentarQueja.js could save 850B (24% reduction).
Minifying http://www.pelayo.com/javascripts/conductores.js could save 764B (40% reduction).
Minifying http://www.pelayo.com/javascripts/jquery.validate.messages_es.js could save 239B (19% reduction).

priority - 4Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking script resources. This causes a delay in rendering your page.

Remove render-blocking JavaScript:

http://www.pelayo.com/javascripts/jquery.js

priority - 1Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 11.8KiB (24% reduction).

Minifying http://www.pelayo.com/stylesheets/pelayocom.css could save 11.1KiB (24% reduction) after compression.
Minifying http://www.pelayo.com/stylesheets/pelayocom_print.css could save 355B (13% reduction) after compression.
Minifying http://www.pelayo.com/stylesheets/colorbox.css could save 232B (30% reduction) after compression.
Minifying http://www.pelayo.com/stylesheets/pelayocom_adds.css could save 212B (27% reduction) after compression.

priority - 1Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 6.5KiB (68% reduction).

Compressing http://www.pelayo.com/images/controls.png could save 2.7KiB (97% reduction).
Compressing http://www.pelayo.com/images/bg_main_menu.png could save 1.1KiB (90% reduction).
Compressing http://www.pelayo.com/images/bg_footer.png could save 1.1KiB (86% reduction).
Compressing http://www.pelayo.com/MFTP/Images/fixed/tarjetas.gif could save 945B (54% reduction).
Compressing http://www.pelayo.com/images/bg_phone_footer.gif could save 669B (33% reduction).
Compressing http://www.pelayo.com/images/aspa-faldon-com.png could save 103B (18% reduction).

pelayo.com Desktop Resource Breakdown

Total Resources132
Number of Hosts49
Static Resources49
JavaScript Resources26
CSS Resources5

pelayo.com mobile page speed rank

Last tested: 2018-12-25


Mobile Speed Bad
61/100

pelayo.com Mobile Speed Test Quick Summary


priority - 39Enable compression

Compressing resources with gzip or deflate can reduce the number of bytes sent over the network.

Enable compression for the following resources to reduce their transfer size by 383.2KiB (72% reduction).

Compressing http://m.pelayo.com/wp-includes/js/jquery/jquery.js?ver=1.11.3 could save 61.2KiB (65% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframewor…3.0.5.min.js?ver=3.0.5 could save 60.2KiB (80% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfshortcod…/bootstrap.css?ver=3.0 could save 47.2KiB (86% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/js/icoroll.js?ver=1.3 could save 20.5KiB (80% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfshortcod…wesome.min.css?ver=3.2 could save 20.1KiB (77% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/style.css?ver=1.0 could save 17.6KiB (76% reduction).
Compressing http://m.pelayo.com/ could save 17.2KiB (73% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframewor…lider-min.js?ver=2.2.0 could save 14.9KiB (71% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/contact-for…?ver=3.51.0-2014.06.20 could save 9.2KiB (61% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/js/modernizr.min.js?ver=2.6.2 could save 8.8KiB (59% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/js/add2home.js?ver=1.0.0 could save 8.7KiB (62% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/contact-for…s/scripts.js?ver=4.3.1 could save 8.4KiB (72% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/js/owl.carousel.min.js?ver=1.0.0 could save 7.9KiB (55% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/css/normalize.css?ver=1.0 could save 6.4KiB (72% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfshortcod…otstrap.min.js?ver=3.0 could save 6.4KiB (69% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframewor…orbox-min.js?ver=3.0.5 could save 6.2KiB (57% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframewor…uery.easing.js?ver=1.3 could save 6KiB (75% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfshortcodes/css/style.css?ver=1.0 could save 6KiB (76% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/css/theme-css.php?ver=1.0 could save 4.8KiB (76% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/css/owl.carousel.css?ver=1.0 could save 4.7KiB (81% reduction).
Compressing http://m.pelayo.com/wp-includes/js/jquery/jquery-migrate.min.js?ver=1.2.1 could save 4KiB (57% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/css/icoroll.css?ver=1.0 could save 4KiB (73% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframewor…exslider.css?ver=2.2.0 could save 3.8KiB (68% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframework/css/style.css?ver=1.0 could save 3.4KiB (73% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframewor…colorbox.css?ver=2.2.0 could save 2.9KiB (67% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframework/css/shadows.css?ver=1.0 could save 2.8KiB (78% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/css/add2home.css?ver=1.0 could save 2.7KiB (49% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/eu-cookie-law/css/style.css?ver=4.4 could save 2.5KiB (71% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframewor…otoswipe.css?ver=2.2.0 could save 2.3KiB (67% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/js/conditionizr.min.js?ver=2.2.0 could save 2KiB (61% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfshortcod…respond.min.js?ver=3.0 could save 1.9KiB (50% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/css/typography.php?ver=1.0 could save 1.7KiB (80% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframewor…ousewheel.js?ver=3.0.6 could save 1.4KiB (60% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/eu-cookie-law/js/scripts.js?ver=4.4 could save 1.2KiB (64% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/js/theme-scripts.php?ver=1.0.0 could save 1.1KiB (55% reduction).
Compressing http://m.pelayo.com/wp-includes/js/wp-embed.min.js?ver=4.4 could save 752B (50% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfshortcod…s/fluidvids.js?ver=3.0 could save 650B (55% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/contact-for…s/styles.css?ver=4.3.1 could save 630B (57% reduction).
Compressing http://m.pelayo.com/wp-content/plugins/wmfframework/js/klass.min.js?ver=1.0 could save 572B (48% reduction).
Compressing http://m.pelayo.com/wp-content/themes/bean/css/dark.css?ver=1.0 could save 522B (57% reduction).

priority - 9Leverage browser caching

Setting an expiry date or a maximum age in the HTTP headers for static resources instructs the browser to load previously downloaded resources from local disk rather than over the network.

Leverage browser caching for the following cacheable resources:

http://m.pelayo.com/wp-content/plugins/wmfframework/images/overlay.png (expiration not specified)
http://m.pelayo.com/wp-content/themes/bean/images/loading-black.gif (expiration not specified)
http://m.pelayo.com/wp-content/uploads/2015/07/RSS.png (expiration not specified)
http://m.pelayo.com/wp-content/uploads/2015/07/contacto_on.png (expiration not specified)
http://m.pelayo.com/wp-content/uploads/2015/07/logo_pelayo.png (expiration not specified)
http://m.pelayo.com/wp-content/uploads/2015/07/menu_btn.png (expiration not specified)
http://m.pelayo.com/wp-content/uploads/2015/12/tarjetas.gif (expiration not specified)
http://m.pelayo.com/wp-content/uploads/2015/12/verisign-logo.gif (expiration not specified)
http://m.pelayo.com/wp-content/uploads/2018/10/home_grua@2x.jpg (expiration not specified)
http://www.googletagmanager.com/gtm.js?id=GTM-TWR7G4 (15 minutes)
http://c1.rfihub.net/js/tc.min.js (60 minutes)
http://www.google-analytics.com/analytics.js (2 hours)

priority - 8Eliminate render-blocking JavaScript and CSS in above-the-fold content

Your page has 1 blocking CSS resources. This causes a delay in rendering your page.

Optimize CSS Delivery of the following:

http://m.pelayo.com/wp-content/plugins/wmfframework/css/style.css?ver=1.0

priority - 4Optimize images

Properly formatting and compressing images can save many bytes of data.

Optimize the following images to reduce their size by 43.5KiB (24% reduction).

Compressing http://m.pelayo.com/wp-content/uploads/2018/10/home_grua@2x.jpg could save 41.8KiB (24% reduction).
Compressing http://m.pelayo.com/wp-content/uploads/2015/07/contacto_on.png could save 1,002B (24% reduction).
Compressing http://m.pelayo.com/wp-content/uploads/2015/07/menu_btn.png could save 753B (64% reduction).

priority - 3Minify CSS

Compacting CSS code can save many bytes of data and speed up download and parse times.

Minify CSS for the following resources to reduce their size by 28.8KiB (21% reduction).

Minifying http://m.pelayo.com/wp-content/plugins/wmfshortcod…/bootstrap.css?ver=3.0 could save 6.8KiB (13% reduction).
Minifying http://m.pelayo.com/wp-content/themes/bean/css/normalize.css?ver=1.0 could save 6.4KiB (72% reduction).
Minifying http://m.pelayo.com/wp-content/themes/bean/style.css?ver=1.0 could save 4.8KiB (22% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfshortcodes/css/style.css?ver=1.0 could save 2.1KiB (28% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfframewor…exslider.css?ver=2.2.0 could save 1.2KiB (23% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfframewor…colorbox.css?ver=2.2.0 could save 1.1KiB (25% reduction).
Minifying http://m.pelayo.com/wp-content/themes/bean/css/icoroll.css?ver=1.0 could save 916B (17% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfframework/css/style.css?ver=1.0 could save 888B (19% reduction).
Minifying http://m.pelayo.com/wp-content/themes/bean/css/owl.carousel.css?ver=1.0 could save 880B (15% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfframewor…otoswipe.css?ver=2.2.0 could save 775B (22% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/eu-cookie-law/css/style.css?ver=4.4 could save 748B (22% reduction).
Minifying http://m.pelayo.com/wp-content/themes/bean/css/theme-css.php?ver=1.0 could save 690B (11% reduction).
Minifying http://m.pelayo.com/wp-content/themes/bean/css/add2home.css?ver=1.0 could save 604B (11% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfframework/css/shadows.css?ver=1.0 could save 471B (13% reduction).
Minifying http://m.pelayo.com/wp-content/themes/bean/css/dark.css?ver=1.0 could save 356B (39% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/contact-for…s/styles.css?ver=4.3.1 could save 147B (14% reduction).

priority - 2Minify JavaScript

Compacting JavaScript code can save many bytes of data and speed up downloading, parsing, and execution time.

Minify JavaScript for the following resources to reduce their size by 21.1KiB (32% reduction).

Minifying http://m.pelayo.com/wp-content/themes/bean/js/icoroll.js?ver=1.3 could save 8.8KiB (35% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfframewor…uery.easing.js?ver=1.3 could save 4.4KiB (55% reduction).
Minifying http://m.pelayo.com/wp-content/themes/bean/js/add2home.js?ver=1.0.0 could save 3.2KiB (23% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/contact-for…s/scripts.js?ver=4.3.1 could save 2KiB (18% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfframewor…ousewheel.js?ver=3.0.6 could save 1.1KiB (46% reduction).
Minifying http://m.pelayo.com/wp-content/themes/bean/js/theme-scripts.php?ver=1.0.0 could save 904B (44% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfshortcod…s/fluidvids.js?ver=3.0 could save 352B (30% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/eu-cookie-law/js/scripts.js?ver=4.4 could save 329B (18% reduction).
Minifying http://m.pelayo.com/wp-content/plugins/wmfframework/js/klass.min.js?ver=1.0 could save 161B (14% reduction).

priority - 1Reduce server response time

In our test, your server responded in 0.30 seconds.

priority - 0Minify HTML

Compacting HTML code, including any inline JavaScript and CSS contained in it, can save many bytes of data and speed up download and parse times.

Minify HTML for the following resources to reduce their size by 3.5KiB (15% reduction).

Minifying http://m.pelayo.com/ could save 3.5KiB (15% reduction).

pelayo.com Mobile Resource Breakdown

Total Resources135
Number of Hosts48
Static Resources14
JavaScript Resources25
CSS Resources20

pelayo.com mobile page usability

Last tested: 2018-12-25


Mobile Usability Good
100/100

pelayo.com HTML validation

Errors

Almost standards mode doctype. Expected “<!DOCTYPE html>”.

Line: 8 Column: 1 - 58
"... <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html..."

Bad value “es_ES” for attribute “lang” on element “html”: The language subtag “es_es” is not a valid language subtag.

Line: 9 Column: 59 - 73
"...onal.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="es_ES" lang="es_ES"> <head..."

Internal encoding declaration “iso-8859-1” disagrees with the actual encoding of the document (“utf-8”).

Line: 16 Column: 1 - 74
"...romos --> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <met..."

Bad value “text/html; charset=iso-8859-1” for attribute “content” on element “meta”: “iso-8859-1” is not a preferred encoding name. The preferred label for this encoding is “windows-1252”.

Line: 16 Column: 1 - 74
"...romos --> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> <met..."

Bad start tag in “img” in “head”.

Line: 41 Column: 1 - 104
"...oscript> <img src="https://tracker.marinsm.com/tp?act=1&cid=820085u26784&script=no" alt="Marin tracker pixel" > </nosc..."

Element “head” is missing a required instance of child element “title”.

Line: 41 Column: 1 - 104
"...oscript> <img src="https://tracker.marinsm.com/tp?act=1&cid=820085u26784&script=no" alt="Marin tracker pixel" > </nosc..."

Stray end tag “noscript”.

Line: 42 Column: 1 - 11
"...pixel" > </noscript> <!--..."

Element “title” not allowed as child of element “body” in this context. (Suppressing further errors from this subtree.)

Line: 46 Column: 1 - 7
"...omo.css"> <title>Difere..."

The “charset” attribute on the “link” element is obsolete. Use an HTTP Content-Type header on the linked resource instead.

Line: 56 Column: 1 - 111
"...</script> <link rel="stylesheet" href="http://www.pelayo.com/stylesheets/pelayocom.css" type="text/css" charset="utf-8"/> <link..." Line: 57 Column: 1 - 116
"..."utf-8"/> <link rel="stylesheet" href="http://www.pelayo.com/stylesheets/pelayocom_adds.css" type="text/css" charset="utf-8"/> <link..." Line: 59 Column: 1 - 17
"..."utf-8"/> <link rel="stylesheet" href="http://www.pelayo.com/stylesheets/pelayocom_print.css" type="text/css" media="print" charset="utf-8"/> <link..." Line: 61 Column: 1 - 17
"..."utf-8"/> <link rel="stylesheet" href="http://www.pelayo.com/stylesheets/colorbox.css" type="text/css" media="screen" charset="utf-8"/> <scri..."

Stray end tag “head”.

Line: 110 Column: 1 - 7
"...</script> </head> <body..."

Start tag “body” seen but an element of the same type was already open.

Line: 111 Column: 1 - 6
"...> </head> <body> <ul i..."

Malformed byte sequence: “f3”.

Line: 131 Column: - 257
"......" Line: 336 Column: - 40
"......" Line: 336 Column: - 56
"......" Line: 344 Column: - 140
"......" Line: 344 Column: - 151
"......" Line: 413 Column: - 133
"......" Line: 413 Column: - 222
"......" Line: 413 Column: - 407
"......" Line: 819 Column: - 38
"......" Line: 844 Column: - 107
"......" Line: 844 Column: - 138
"......" Line: 906 Column: - 95
"......" Line: 906 Column: - 122
"......" Line: 937 Column: - 84
"......" Line: 937 Column: - 95
"......" Line: 937 Column: - 105
"......" Line: 937 Column: - 111
"......" Line: 937 Column: - 122
"......" Line: 937 Column: - 132
"......" Line: 986 Column: - 14
"......" Line: 1073 Column: - 93
"......" Line: 1073 Column: - 112
"......" Line: 1398 Column: - 167
"......" Line: 1446 Column: - 131
"......"

Malformed byte sequence: “e1”.

Line: 336 Column: - 30
"......" Line: 341 Column: - 14
"......" Line: 341 Column: - 146
"......" Line: 346 Column: - 120
"......" Line: 346 Column: - 333
"......" Line: 1233 Column: - 77
"......"

Element “h1” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Line: 334 Column: 1 - 4
"...mos"> <h1> <div ..."

Malformed byte sequence: “f1”.

Line: 414 Column: - 194
"......" Line: 414 Column: - 425
"......"

Bad value “_new” for attribute “target” on element “a”: Reserved keyword “new” used.

Line: 603 Column: 1 - 58
"...> <a href="http://www.agropelayo.com/" title="" target=_new>Seguro..." Line: 1430 Column: 1 - 271
"... <a href="https://www.telesor.es/telesor_embedded.php?id=512181&idTelesor=41&tId=1&KeepThis=true&TB_iframe=true" title="" target=_new onclick="pageVisitHome('https://www.telesor.es/telesor_embedded.php?id=512181&idTelesor=41&tId=1&KeepThis=true&TB_iframe=true');">Discapacitados..."

Malformed byte sequence: “e9”.

Line: 968 Column: - 86
"......" Line: 968 Column: - 113
"......" Line: 1233 Column: - 590
"......"

Malformed byte sequence: “a1”.

Line: 1233 Column: - 71
"......"

Malformed byte sequence: “ed”.

Line: 1234 Column: - 72
"......" Line: 1234 Column: - 257
"......"

Element “br” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Line: 1231 Column: 1 - 6
"...> <ul> <br /> <div>..."

Element “div” not allowed as child of element “ul” in this context. (Suppressing further errors from this subtree.)

Line: 1232 Column: 1 - 5
"... <br /> <div> <a h..."

The “align” attribute on the “img” element is obsolete. Use CSS instead.

Line: 1446 Column: 60 - 154
"...okie();"> <img align="left" src="/images/aspa-faldon-com.png" alt="Cerrar el fald�n y aceptar cookies" /> </a> ..."

Malformed byte sequence: “bf”.

Line: 1463 Column: - 55
"......"

The hash-name reference in attribute “usemap” referred to “botontmap3”, but there is no “map” element with a “name” attribute with that value.

Line: 336 Column: 2 - 243
"...ative;"> <img alt="Consigue este fant�stico bal�n de la Selecci�n al contratar tu seguro de coche o moto" height="556" src="http://www.pelayo.com/MFTP/Images/promos/home/home_promo_balon@2x.jpg" style="border: 0px;" usemap="#botontmap3" width="711" /> <div..."

Warnings

The “border” attribute is obsolete. Consider specifying “img { border: 0; }” in CSS instead.

Line: 128 Column: 70 - 168
"... la home"><img border="0" id="logCabec" src="//www.pelayo.com/images/pelayocom.gif" title="www.pelayo.com" /></a> <..."

pelayo.com similar domains

Similar domains:
www.pelayo.com
www.pelayo.net
www.pelayo.org
www.pelayo.info
www.pelayo.biz
www.pelayo.us
www.pelayo.mobi
www.elayo.com
www.pelayo.com
www.oelayo.com
www.poelayo.com
www.opelayo.com
www.lelayo.com
www.plelayo.com
www.lpelayo.com
www.playo.com
www.pwlayo.com
www.pewlayo.com
www.pwelayo.com
www.pslayo.com
www.peslayo.com
www.pselayo.com
www.pdlayo.com
www.pedlayo.com
www.pdelayo.com
www.prlayo.com
www.perlayo.com
www.prelayo.com
www.peayo.com
www.pepayo.com
www.pelpayo.com
www.peplayo.com
www.peoayo.com
www.peloayo.com
www.peolayo.com
www.pekayo.com
www.pelkayo.com
www.peklayo.com
www.pelyo.com
www.pelqyo.com
www.pelaqyo.com
www.pelqayo.com
www.pelwyo.com
www.pelawyo.com
www.pelwayo.com
www.pelsyo.com
www.pelasyo.com
www.pelsayo.com
www.pelzyo.com
www.pelazyo.com
www.pelzayo.com
www.pelao.com
www.pelato.com
www.pelayto.com
www.pelatyo.com
www.pelago.com
www.pelaygo.com
www.pelagyo.com
www.pelaho.com
www.pelayho.com
www.pelahyo.com
www.pelauo.com
www.pelayuo.com
www.pelauyo.com
www.pelay.com
www.pelayi.com
www.pelayoi.com
www.pelayio.com
www.pelayk.com
www.pelayok.com
www.pelayko.com
www.pelayl.com
www.pelayol.com
www.pelaylo.com
www.pelayp.com
www.pelayop.com
www.pelaypo.com
www.pelayo.con

pelayo.com Ping

Ping is a computer network administration software utility used to test the reachability of a host on an Internet Protocol (IP) network. It measures the round-trip time for messages sent from the originating host to a destination computer that are echoed back to the source.


pelayo.com TRACEROUTE

Traceroute is a computer network diagnostic tool for displaying the route (path) and measuring transit delays of packets across an Internet Protocol (IP) network. The history of the route is recorded as the round-trip times of the packets received from each successive host (remote node) in the route (path); the sum of the mean times in each hop is a measure of the total time spent to establish the connection. Traceroute proceeds unless all (three) sent packets are lost more than twice, then the connection is lost and the route cannot be evaluated.