2.7 sec in total
344 ms
2.2 sec
145 ms
Click here to check amazing Hora content for Mexico. Otherwise, check out these important facts you probably never knew about hora.es
Ponte al día de toda la actualidad del mundo con nuestras noticias y reseñas. Además, puedes consultar la hora actual de cualquier parte del planeta.
Visit hora.esWe analyzed Hora.es page load time and found that the first response time was 344 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
hora.es performance score
name
value
score
weighting
Value3.8 s
27/100
10%
Value12.0 s
0/100
25%
Value13.8 s
1/100
10%
Value4,720 ms
0/100
30%
Value0.412
24/100
15%
Value25.0 s
0/100
10%
344 ms
563 ms
11 ms
212 ms
24 ms
Our browser made a total of 79 requests to load all elements on the main page. We found that 35% of them (28 requests) were addressed to the original Hora.es, 9% (7 requests) were made to Apis.google.com and 8% (6 requests) were made to Pagead2.googlesyndication.com. The less responsive or slowest element that took the longest time to load (669 ms) belongs to the original domain Hora.es.
Page size can be reduced by 848.0 kB (63%)
1.3 MB
491.1 kB
In fact, the total size of Hora.es main page is 1.3 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. 65% of websites need less resources to load. Javascripts take 900.1 kB which makes up the majority of the site volume.
Potential reduce by 179.0 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 179.0 kB or 74% of the original size.
Potential reduce by 4.4 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. Hora images are well optimized though.
Potential reduce by 560.5 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 560.5 kB or 62% of the original size.
Potential reduce by 104.1 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. Hora.es needs all CSS files to be minified and compressed as it can save up to 104.1 kB or 83% of the original size.
Number of requests can be reduced by 42 (60%)
70
28
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 34 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
hora.es
344 ms
www.hora.es
563 ms
bootstrap.min.css
11 ms
hora.css
212 ms
css
24 ms
css
38 ms
adsbygoogle.js
17 ms
reloj.js
236 ms
jquery.min.js
29 ms
bootstrap.min.js
4 ms
jquery.cookie.min.js
143 ms
hora.js
264 ms
js
75 ms
mustache.min.js
304 ms
jquery.mustache.js
304 ms
weather.css
304 ms
weather.js
304 ms
google_search.js
303 ms
gpt.js
30 ms
background.jpg
332 ms
logo_es.png
307 ms
lang-es.png
306 ms
lang-gb.png
669 ms
lang-ru.png
312 ms
lang-pt.png
311 ms
lang-br.png
422 ms
continent-north-america.png
418 ms
continent-central-america.png
433 ms
continent-south-america.png
435 ms
continent-asia.png
438 ms
continent-europa.png
560 ms
continent-africa.png
560 ms
continent-australia.png
568 ms
ca-pub-8412499929002098.js
50 ms
zrt_lookup.html
123 ms
show_ads_impl.js
89 ms
ODelI1aHBYDBqgeIAH2zlNzbP97U9sKh0jjxbPbfOKg.ttf
116 ms
toadOcfmlt9b38dHJxOBGEMbjGELOEJD5J8DUmxkO-A.ttf
121 ms
font
120 ms
pubads_impl_81.js
39 ms
loading.gif
530 ms
glyphicons-halflings-regular.woff
27 ms
plusone.js
153 ms
analytics.js
81 ms
ads
347 ms
container.html
91 ms
pla
61 ms
like.php
134 ms
collect
23 ms
bootstrap.html
369 ms
home.html
459 ms
cb=gapi.loaded_0
22 ms
cb=gapi.loaded_1
47 ms
fastbutton
100 ms
vpc6VNjRPXV.js
165 ms
LVx-xkvaJ0b.png
199 ms
postmessageRelay
39 ms
api.js
33 ms
core:rpc:shindig.random:shindig.sha1.js
65 ms
2536007149-postmessagerelay.js
64 ms
cb=gapi.loaded_0
32 ms
cb=gapi.loaded_1
24 ms
expansion_embed.js
12 ms
osd.js
24 ms
m_js_controller.js
29 ms
abg.js
43 ms
favicon
68 ms
googlelogo_color_112x36dp.png
48 ms
favicon
74 ms
nessie_icon_tiamat_white.png
38 ms
s
27 ms
x_button_blue2.png
12 ms
common.js
23 ms
util.js
56 ms
controls.js
49 ms
places_impl.js
47 ms
ui
44 ms
powered-by-google-on-white3.png
53 ms
autocomplete-icons.png
62 ms
hora.es accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
hora.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
hora.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 doesn't use legible font sizes
Tap targets are not sized appropriately
ES
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hora.es 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 Hora.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.
hora.es
Open Graph description is not detected on the main page of Hora. 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: