Report Summary

  • 63

    Performance

    Renders faster than
    77% of other websites

  • 73

    Accessibility

    Visual factors better than
    that of 38% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

disanz.es

Disanz distribuidor online de material escolar y de oficina

Page Load Speed

6.7 sec in total

First Response

190 ms

Resources Loaded

3.1 sec

Page Rendered

3.5 sec

About Website

Welcome to disanz.es homepage info - get ready to check Disanz best content for Spain right away, or after learning these important things about disanz.es

Disanz es el distribuidor online de referencia con los mejores descuentos en productos de material escolar y de oficina

Visit disanz.es

Key Findings

We analyzed Disanz.es page load time and found that the first response time was 190 ms and then it took 6.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

disanz.es performance score

63

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value5.4 s

56/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.007

100/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

disanz.es

190 ms

disanz.es

399 ms

bundle.min.css

403 ms

temp2.css

371 ms

bannerminil.jpg

1189 ms

Our browser made a total of 96 requests to load all elements on the main page. We found that 93% of them (89 requests) were addressed to the original Disanz.es, 4% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Privacypolicies.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Disanz.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 120.7 kB (4%)

Content Size

3.2 MB

After Optimization

3.1 MB

In fact, the total size of Disanz.es main page is 3.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. 50% of websites need less resources to load. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 50.0 kB

  • Original 55.6 kB
  • After minification 34.7 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 21.0 kB, which is 38% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 50.0 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 9.8 kB

  • Original 2.9 MB
  • After minification 2.9 MB

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. Disanz images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 28.7 kB

  • Original 177.4 kB
  • After minification 177.4 kB
  • After compression 148.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 28.7 kB or 16% of the original size.

CSS Optimization

-41%

Potential reduce by 32.1 kB

  • Original 78.1 kB
  • After minification 78.1 kB
  • After compression 46.0 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. Disanz.es needs all CSS files to be minified and compressed as it can save up to 32.1 kB or 41% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

89

After Optimization

89

The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Disanz. According to our analytics all requests are already optimized.

Accessibility Review

disanz.es accessibility score

73

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

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

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

disanz.es best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

High

Page has valid source maps

SEO Factors

disanz.es SEO score

91

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    ES

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Disanz.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 Disanz.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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Disanz. 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: