1.6 sec in total
70 ms
1.4 sec
132 ms
Welcome to hp.es homepage info - get ready to check HP best content right away, or after learning these important things about hp.es
Más información sobre impresoras, portátiles, ordenadores de sobremesa y más en el sitio web oficial de HP®
Visit hp.esWe analyzed Hp.es page load time and found that the first response time was 70 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
hp.es performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value10.1 s
0/100
25%
Value9.4 s
12/100
10%
Value4,030 ms
1/100
30%
Value0.224
56/100
15%
Value22.7 s
1/100
10%
70 ms
63 ms
63 ms
67 ms
10 ms
Our browser made a total of 41 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Hp.es, 29% (12 requests) were made to Www8-hp.com and 7% (3 requests) were made to Nexus.ensighten.com. The less responsive or slowest element that took the longest time to load (628 ms) relates to the external source Www8-hp.com.
Page size can be reduced by 1.3 MB (75%)
1.8 MB
439.9 kB
In fact, the total size of Hp.es main page is 1.8 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. 55% of websites need less resources to load. Javascripts take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 94.9 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 94.9 kB or 88% of the original size.
Potential reduce by 1.2 MB
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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.2 MB or 75% of the original size.
Number of requests can be reduced by 19 (51%)
37
18
The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of HP. 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 as a result speed up the page load time.
home.html
70 ms
hpi-fontface-core.css
63 ms
hpi-hf.css
63 ms
homepage.css
67 ms
mootools-core-compat.js
10 ms
mootools-more-compat.js
5 ms
hpi-hf-m.js
46 ms
hpi-autocomplete-loader-2-m.js
5 ms
hpi-autocomplete-loader-store-m.js
13 ms
hpi-hf-init-m.js
13 ms
hpi-caas-privacy-cookie.js
50 ms
home-init-hpe.js
12 ms
hpweb_geolocation.js
13 ms
abmvt2.js
5 ms
metrics.js
7 ms
Bootstrap.js
35 ms
2129670914.js
16 ms
serverComponent.php
207 ms
event
112 ms
2129670914.html
332 ms
geo2.js
31 ms
event
257 ms
hpi-hp-logo.gif
19 ms
hpi-hp-logo-pr.gif
47 ms
s.gif
20 ms
latin-e-regular-ttf.ttf
628 ms
latin-e-regular-ttf.ttf
301 ms
709ff366898ce20345c18b891bd30ac9.js
155 ms
event
150 ms
hpi-flag.png
204 ms
hpi-hf-icons-ttf.ttf
202 ms
privacy_cookie.JS
155 ms
ladybug.jsp
248 ms
hpi_ES_ES_HHO_PSG_spectre-x2_20160315_tcm176-2195646.jpg
60 ms
s-homepage-hpe.gif
85 ms
qualtricsSurvey.js
21 ms
bk-coretag.js
13 ms
s65172272941563
29 ms
13555
56 ms
s-hf-hpe_462697.gif
35 ms
s64392503292765
16 ms
hp.es accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Some elements have a [tabindex] value greater than 0
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
hp.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
hp.es SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hp.es can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed Spanish language. Our system also found out that Hp.es 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.
hp.es
Open Graph description is not detected on the main page of HP. 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: