3.2 sec in total
305 ms
2.6 sec
259 ms
Welcome to lezo.net homepage info - get ready to check Lezo best content right away, or after learning these important things about lezo.net
Lezoko Unibertsitateko Udalaren web ofiziala. Herriko informaziorik osatuena. Albisteak, kultura agenda, jarduerak...
Visit lezo.netWe analyzed Lezo.net page load time and found that the first response time was 305 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
lezo.net performance score
name
value
score
weighting
Value2.8 s
55/100
10%
Value4.0 s
50/100
25%
Value4.6 s
70/100
10%
Value40 ms
100/100
30%
Value0.004
100/100
15%
Value5.1 s
75/100
10%
305 ms
897 ms
183 ms
190 ms
191 ms
Our browser made a total of 51 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Lezo.net, 94% (48 requests) were made to Lezo.eus and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (897 ms) relates to the external source Lezo.eus.
Page size can be reduced by 252.9 kB (21%)
1.2 MB
972.5 kB
In fact, the total size of Lezo.net main page is 1.2 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. 30% of websites need less resources to load. Images take 957.3 kB which makes up the majority of the site volume.
Potential reduce by 24.1 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 24.1 kB or 79% of the original size.
Potential reduce by 55.7 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. Lezo images are well optimized though.
Potential reduce by 102.7 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 102.7 kB or 68% of the original size.
Potential reduce by 70.4 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. Lezo.net needs all CSS files to be minified and compressed as it can save up to 70.4 kB or 82% of the original size.
Number of requests can be reduced by 27 (55%)
49
22
The browser has sent 49 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lezo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
lezo.net
305 ms
www.lezo.eus
897 ms
aggregator.css
183 ms
book.css
190 ms
node.css
191 ms
defaults.css
191 ms
system.css
191 ms
system-menus.css
193 ms
user.css
273 ms
content-module.css
281 ms
ckeditor.css
282 ms
cutemenu.css
281 ms
date.css
285 ms
filefield.css
283 ms
tinydropdown.css
365 ms
extlink.css
371 ms
fieldgroup.css
373 ms
style.css
559 ms
lezo.css
375 ms
jquery.min.js
566 ms
drupal.js
456 ms
eu_f145bb1bed8bec6b48c84b7f213f6bef.js
463 ms
cutemenu.js
464 ms
tinydropdown.js
467 ms
extlink.js
548 ms
jquery.cycle.all.js
738 ms
textarea.js
576 ms
hoverIntent.js
576 ms
superfish.js
640 ms
onepixelout.js
570 ms
ga.js
88 ms
body-back1.png
96 ms
danland_logo.png
99 ms
searchbox-black.png
101 ms
lezo-ayunta.png
102 ms
facebook-top.png
98 ms
twitter-top.png
96 ms
rss-top.png
187 ms
mail-top.png
190 ms
home_97.jpg
566 ms
uxue6.jpg
602 ms
homezinegoak.jpg
566 ms
importancia-vida-activa-ninos-y-deportes-1024x538.jpg
744 ms
tunela_1.jpg
647 ms
muesca-berri-1.png
223 ms
extlink.png
315 ms
grippie.png
409 ms
mailto.png
503 ms
folion-webfont.ttf
597 ms
folio_bold_condensed_bt-webfont.ttf
599 ms
__utm.gif
12 ms
lezo.net 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
Image elements do not have [alt] attributes
Links do not have a discernible name
lezo.net 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
lezo.net 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
EU
EU
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lezo.net can be misinterpreted by Google and other search engines. Our service has detected that Basque is used on the page, and it matches the claimed language. Our system also found out that Lezo.net 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.
lezo.net
Open Graph description is not detected on the main page of Lezo. 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: