Report Summary

  • 78

    Performance

    Renders faster than
    85% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

lezo.net

| Lezo.eus

Page Load Speed

3.2 sec in total

First Response

305 ms

Resources Loaded

2.6 sec

Page Rendered

259 ms

lezo.net screenshot

About Website

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.net

Key Findings

We 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.

Performance Metrics

lezo.net performance score

78

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

55/100

10%

LCP (Largest Contentful Paint)

Value4.0 s

50/100

25%

SI (Speed Index)

Value4.6 s

70/100

10%

TBT (Total Blocking Time)

Value40 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.004

100/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

lezo.net

305 ms

www.lezo.eus

897 ms

aggregator.css

183 ms

book.css

190 ms

node.css

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 Optimization Overview & Recommendations

Page size can be reduced by 252.9 kB (21%)

Content Size

1.2 MB

After Optimization

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.

HTML Optimization

-79%

Potential reduce by 24.1 kB

  • Original 30.7 kB
  • After minification 28.1 kB
  • After compression 6.6 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.

Image Optimization

-6%

Potential reduce by 55.7 kB

  • Original 957.3 kB
  • After minification 901.6 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.

JavaScript Optimization

-68%

Potential reduce by 102.7 kB

  • Original 151.1 kB
  • After minification 121.9 kB
  • After compression 48.4 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.

CSS Optimization

-82%

Potential reduce by 70.4 kB

  • Original 86.2 kB
  • After minification 63.3 kB
  • After compression 15.9 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.

Requests Breakdown

Number of requests can be reduced by 27 (55%)

Requests Now

49

After Optimization

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.

Accessibility Review

lezo.net accessibility score

75

Accessibility Issues

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

lezo.net best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

lezo.net SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EU

  • Language Claimed

    EU

  • Encoding

    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.

Social Sharing Optimization

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: