4.2 sec in total
149 ms
3.7 sec
339 ms
Visit wil.es now to see the best up-to-date Wil content and also check out these interesting facts you probably never knew about wil.es
Wilhelm Rahn is a Product Designer. He helps companies achieve their product goals and create amazing experiences.
Visit wil.esWe analyzed Wil.es page load time and found that the first response time was 149 ms and then it took 4 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
wil.es performance score
name
value
score
weighting
Value4.5 s
15/100
10%
Value5.5 s
18/100
25%
Value6.7 s
36/100
10%
Value440 ms
64/100
30%
Value0.407
24/100
15%
Value8.9 s
34/100
10%
149 ms
97 ms
46 ms
53 ms
22 ms
Our browser made a total of 89 requests to load all elements on the main page. We found that 81% of them (72 requests) were addressed to the original Wil.es, 3% (3 requests) were made to Fonts.googleapis.com and 3% (3 requests) were made to S.gravatar.com. The less responsive or slowest element that took the longest time to load (772 ms) belongs to the original domain Wil.es.
Page size can be reduced by 442.9 kB (61%)
724.2 kB
281.3 kB
In fact, the total size of Wil.es main page is 724.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 419.2 kB which makes up the majority of the site volume.
Potential reduce by 25.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 25.5 kB or 75% of the original size.
Potential reduce by 1.1 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. Wil images are well optimized though.
Potential reduce by 265.9 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 265.9 kB or 63% of the original size.
Potential reduce by 150.3 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. Wil.es needs all CSS files to be minified and compressed as it can save up to 150.3 kB or 84% of the original size.
Number of requests can be reduced by 40 (78%)
51
11
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wil. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 28 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
wil.es
149 ms
www.wil.es
97 ms
css
46 ms
css
53 ms
style.css
22 ms
styles.css
15 ms
video-js.css
24 ms
jquery.fancybox-1.3.4.css
25 ms
jetpack.css
20 ms
jquery.js
28 ms
jquery-migrate.min.js
22 ms
selectnav.min.js
25 ms
video.js
26 ms
css
58 ms
comment-reply.min.js
27 ms
jquery.form.min.js
29 ms
scripts.js
30 ms
devicepx-jetpack.js
13 ms
gprofiles.js
57 ms
wpgroho.js
29 ms
jquery.flexslider-min.js
29 ms
froogaloop.min.js
30 ms
jquery.isotope.min.js
34 ms
jquery.infinitescroll.min.js
30 ms
jquery.ba-bbq.min.js
31 ms
tweetMachine.js
41 ms
jquery.jribbble.js
31 ms
jquery.validate.min.js
32 ms
audio.min.js
36 ms
jquery.fancybox-1.3.4.pack.js
34 ms
plugins.js
35 ms
main.js
36 ms
user.js
37 ms
e-201536.js
25 ms
styles.css
30 ms
style.css
33 ms
jetpack.css
757 ms
jquery-migrate.min.js
772 ms
video-js.css
761 ms
jquery.fancybox-1.3.4.css
761 ms
selectnav.min.js
762 ms
video.js
33 ms
jquery.js
89 ms
comment-reply.min.js
108 ms
jquery.form.min.js
131 ms
scripts.js
135 ms
wpgroho.js
141 ms
jquery.flexslider-min.js
162 ms
froogaloop.min.js
165 ms
jquery.infinitescroll.min.js
192 ms
jquery.ba-bbq.min.js
228 ms
jquery.jribbble.js
245 ms
jquery.isotope.min.js
260 ms
jquery.validate.min.js
274 ms
jquery.fancybox-1.3.4.pack.js
284 ms
plugins.js
295 ms
audio.min.js
300 ms
main.js
326 ms
user.js
331 ms
tweetMachine.js
336 ms
iconic-font.css
368 ms
onepcssgrid.css
385 ms
main.css
398 ms
user.css
747 ms
wp-emoji-release.min.js
89 ms
ga.js
79 ms
headerlogo.png
44 ms
about-me-bar.jpg
42 ms
google-new-logo-featured-378x114.png
42 ms
turquia-378x114.jpg
43 ms
villas-378x114.jpg
43 ms
counter.js
41 ms
headerlogo.png
71 ms
about-me-bar.jpg
111 ms
google-new-logo-featured-378x114.png
109 ms
turquia-378x114.jpg
107 ms
villas-378x114.jpg
109 ms
iconic-font.woff
106 ms
APH4jr0uSos5wiut5cpjronF5uFdDttMLvmWuJdhhgs.ttf
61 ms
__utm.gif
163 ms
t.php
157 ms
widgets.js
70 ms
ajax-loader.gif
28 ms
hovercard.css
42 ms
services.css
52 ms
collect
57 ms
ajax-loader.gif
82 ms
g.gif
6 ms
ga-audiences
32 ms
wil.es accessibility score
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.
wil.es best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
wil.es SEO score
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
EN
ES
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wil.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 Wil.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.
wil.es
Open Graph data is detected on the main page of Wil. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: