2.6 sec in total
336 ms
2 sec
223 ms
Welcome to velocidad.es homepage info - get ready to check Velocidad best content for Spain right away, or after learning these important things about velocidad.es
Prueba de velocidad para medir la velocidad de tu conexión ADSL y cable. Comprobación de la velocidad de subida y bajada de adsl. También funciona para ADSL2+ y VDSL.
Visit velocidad.esWe analyzed Velocidad.es page load time and found that the first response time was 336 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
velocidad.es performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value7.2 s
5/100
25%
Value5.5 s
54/100
10%
Value1,250 ms
19/100
30%
Value0.055
98/100
15%
Value10.6 s
23/100
10%
336 ms
196 ms
16 ms
71 ms
65 ms
Our browser made a total of 139 requests to load all elements on the main page. We found that 4% of them (6 requests) were addressed to the original Velocidad.es, 32% (44 requests) were made to Ajax.googleapis.com and 13% (18 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (489 ms) belongs to the original domain Velocidad.es.
Page size can be reduced by 1.8 MB (78%)
2.3 MB
521.5 kB
In fact, the total size of Velocidad.es main page is 2.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.6 MB which makes up the majority of the site volume.
Potential reduce by 58.5 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 58.5 kB or 78% of the original size.
Potential reduce by 15.3 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. Obviously, Velocidad needs image optimization as it can save up to 15.3 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 309.6 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 309.6 kB or 57% of the original size.
Potential reduce by 1.4 MB
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. Velocidad.es needs all CSS files to be minified and compressed as it can save up to 1.4 MB or 91% of the original size.
Number of requests can be reduced by 96 (81%)
119
23
The browser has sent 119 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Velocidad. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 78 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
velocidad.es
336 ms
wp-emoji-release.min.js
196 ms
styles.css
16 ms
cli-style.css
71 ms
pagenavi-css.css
65 ms
css
69 ms
css
72 ms
js_composer.min.css
29 ms
an-style.min.css
64 ms
style.css
489 ms
style.css
209 ms
jquery.js
65 ms
jquery-migrate.min.js
65 ms
cookielawinfo.js
11 ms
adsbygoogle.js
7 ms
plusone.js
118 ms
472 ms
jquery.form.min.js
61 ms
scripts.js
62 ms
tagdiv_theme.min.js
62 ms
comment-reply.min.js
61 ms
an-scripts.min.js
65 ms
wp-embed.min.js
62 ms
js_composer_front.min.js
61 ms
analytics.js
39 ms
logo-pie-300x100.png
33 ms
vivo-xplay-5-con-6-gb-de-ram-324x235.jpg
70 ms
xiaomi-mi5-nuevo-movil-324x235.jpg
70 ms
dispositivo-wifipill-aparato-movil-324x235.jpg
33 ms
254597764635514.1672.159596170.png
280 ms
estandar-ng-pon2-conexion-de-cables-324x235.jpg
31 ms
android-n-324x235.jpg
31 ms
proyecto-polaris-para-cargar-la-web-mas-rapida-324x235.jpg
30 ms
logo-pie-300x100.png
69 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
39 ms
MTP_ySUJH_bn48VBG8sNSonF5uFdDttMLvmWuJdhhgs.ttf
54 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
119 ms
newspaper.woff
275 ms
xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf
118 ms
PRmiXeptR36kaC0GEAetxrfB31yxOzP-czbf6AAKCVo.ttf
118 ms
PRmiXeptR36kaC0GEAetxi8cqLH4MEiSE0ROcU-qHOA.ttf
118 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
117 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
119 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
124 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
123 ms
ca-pub-9314112849612183.js
108 ms
zrt_lookup.html
108 ms
show_ads_impl.js
108 ms
collect
52 ms
collect
248 ms
cb=gapi.loaded_0
162 ms
widgets.js
126 ms
elements.png
182 ms
jquery.min.js
236 ms
160 ms
268 ms
ads
389 ms
osd.js
66 ms
font-awesome.min.css
60 ms
css
88 ms
css
100 ms
css
112 ms
css
119 ms
css
120 ms
css
121 ms
overlay.png
184 ms
js
128 ms
timeline.d11f7a3b3287fb94220e8ee6d03cc772.js
41 ms
dojo.js
36 ms
cb=gapi.loaded_1
29 ms
cb=gapi.loaded_2
56 ms
badge
195 ms
abg.js
62 ms
000000_new_ico.gif
99 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
142 ms
W4wDsBUluyw0tK3tykhXEfesZW2xOQ-xsNqO47m55DA.ttf
45 ms
OLffGBTaF0XFOW1gnuHF0Z0EAVxt0G0biEntp43Qt6E.ttf
45 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
170 ms
v0SdcGFAl2aezM9Vq_aFTQ.ttf
241 ms
registry.js
87 ms
parser.js
131 ms
Dialog.js
108 ms
syndication
285 ms
607927618839691264
348 ms
postmessageRelay
107 ms
in.php
220 ms
main.js
39 ms
window.js
42 ms
Moveable.js
44 ms
TimedMoveable.js
44 ms
focus.js
97 ms
manager.js
112 ms
_Widget.js
112 ms
_TemplatedMixin.js
111 ms
_CssStateMixin.js
114 ms
_FormMixin.js
138 ms
_DialogMixin.js
172 ms
DialogUnderlay.js
179 ms
ContentPane.js
171 ms
common.js
166 ms
rs=AGLTcCMrizkpiALDnWSyRMZf6aS6n8wvig
71 ms
3193398744-postmessagerelay.js
247 ms
rpc:shindig_random.js
99 ms
url.js
149 ms
stamp.js
157 ms
rs=AGLTcCOFe0ICGMfEiURrBMnTsZI9m_OXug
99 ms
rs=AGLTcCMbFZq9EzXANPBH3V1p_6p-yXCwWw
153 ms
touch.js
181 ms
common.js
181 ms
Mover.js
180 ms
photo.jpg
289 ms
Stateful.js
168 ms
a11y.js
167 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
176 ms
dtpHsbgPEm2lVWciJZ0P-A.ttf
178 ms
bdHGHleUa-ndQCOrdpfxfw.ttf
214 ms
_WidgetBase.js
160 ms
string.js
160 ms
cache.js
160 ms
_OnDijitClickMixin.js
160 ms
_FocusMixin.js
164 ms
uacss.js
164 ms
hccss.js
176 ms
_Container.js
147 ms
_ContentPaneResizeMixin.js
135 ms
html.js
151 ms
loading.js
151 ms
BackgroundIframe.js
141 ms
rs=AGLTcCMbFZq9EzXANPBH3V1p_6p-yXCwWw
60 ms
autoscroll.js
71 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
25 ms
cb=gapi.loaded_0
23 ms
timeline.47ab5d19e8ed22531abcf4f86f3ae53a.light.ltr.css
12 ms
Destroyable.js
34 ms
a11yclick.js
35 ms
rs=AGLTcCMbFZq9EzXANPBH3V1p_6p-yXCwWw
24 ms
Viewport.js
62 ms
utils.js
61 ms
hccss.js
60 ms
velocidad.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
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
Image elements do not have [alt] attributes
Links do not have a discernible name
velocidad.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
Page has valid source maps
velocidad.es SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Image elements do not have [alt] attributes
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
ES
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Velocidad.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it does not match the claimed English language. Our system also found out that Velocidad.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.
velocidad.es
Open Graph data is detected on the main page of Velocidad. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: