Tools & Wizards About Us
enlaze.net screenshot

Report Summary

  • 29

    Performance

    Renders faster than
    49% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 72% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 87

    SEO

    Google-friendlier than
    66% of websites

enlaze.net

enlaze. La operadora de internet y telefonía móvil de Cádiz

Page Load Speed

14.4 sec in total

First Response

3.1 sec

Resources Loaded

9.1 sec

Page Rendered

2.3 sec

enlaze.net screenshot

About Website

Click here to check amazing En La Ze content. Otherwise, check out these important facts you probably never knew about enlaze.net

Enlaze es una operadora de internet y telefonía móvil formada por un equipo de jóvenes gaditanos/as. Porque nosotros somos de aquí, somos como tú.

Visit enlaze.net

Key Findings

We analyzed Enlaze.net page load time and found that the first response time was 3.1 sec and then it took 11.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

enlaze.net performance score

29

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value12.1 s

3/100

10%

TBT (Total Blocking Time)

Value270 ms

82/100

30%

CLS (Cumulative Layout Shift)

Value0.611

10/100

15%

TTI (Time to Interactive)

Value10.3 s

24/100

10%

Network Requests Diagram

www.enlaze.net

3083 ms

jquery-3.3.1.min.js

184 ms

cookie-law-info-public.js

329 ms

popupscript.js

371 ms

sweetalert2.all.min.js

488 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 96% of them (44 requests) were addressed to the original Enlaze.net, 2% (1 request) were made to Cdnjs.cloudflare.com and 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Enlaze.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 794.6 kB (35%)

Content Size

2.3 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Enlaze.net 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 714.1 kB

  • Original 837.1 kB
  • After minification 837.0 kB
  • After compression 123.0 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 714.1 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 60.7 kB

  • Original 1.4 MB
  • After minification 1.3 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. En La Ze images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 19.9 kB

  • Original 96.2 kB
  • After minification 96.2 kB
  • After compression 76.3 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 19.9 kB or 21% of the original size.

Requests Breakdown

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

Requests Now

36

After Optimization

9

  • Images
  • JavaScript

The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of En La Ze. 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 as a result speed up the page load time.

Network Requests Diagram

www.enlaze.net

www.enlaze.net

3083 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

184 ms

cookie-law-info-public.js

cookie-law-info-public.js

329 ms

popupscript.js

popupscript.js

371 ms

sweetalert2.all.min.js

sweetalert2.all.min.js

488 ms

jscolor.js

jscolor.js

498 ms

popper.min.js

popper.min.js

385 ms

bootstrap.min.js

bootstrap.min.js

550 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

462 ms

tiny-slider.js

tiny-slider.js

63 ms

enlaze.js

enlaze.js

548 ms

js

js

137 ms

78948cd001413cdcf12e292fccc6afaf.js

78948cd001413cdcf12e292fccc6afaf.js

1306 ms

lazysizes.min.js

lazysizes.min.js

971 ms

wp-polyfill.min.js

wp-polyfill.min.js

989 ms

hooks.min.js

hooks.min.js

958 ms

i18n.min.js

i18n.min.js

1205 ms

lodash.min.js

lodash.min.js

987 ms

url.min.js

url.min.js

988 ms

api-fetch.min.js

api-fetch.min.js

989 ms

index.js

index.js

990 ms

wp-embed.min.js

wp-embed.min.js

990 ms

texto_viaje.svg

texto_viaje.svg

595 ms

ilus_viaje.svg

ilus_viaje.svg

434 ms

pecha-gigas.jpg

pecha-gigas.jpg

967 ms

pecha-charlar.jpg

pecha-charlar.jpg

2484 ms

bullet.svg

bullet.svg

283 ms

cta-comprueba-cobertura.jpg

cta-comprueba-cobertura.jpg

677 ms

patron-cadiz.svg

patron-cadiz.svg

1024 ms

MohrRounded-Regular.woff

MohrRounded-Regular.woff

487 ms

MohrRounded-Medium.woff

MohrRounded-Medium.woff

1318 ms

MohrRounded-Light.woff

MohrRounded-Light.woff

540 ms

MohrRounded-ExtraLight.woff

MohrRounded-ExtraLight.woff

1268 ms

MohrRounded-Thin.woff

MohrRounded-Thin.woff

1268 ms

MohrRounded-SemiBold.woff

MohrRounded-SemiBold.woff

1269 ms

MohrRounded-Bold.woff

MohrRounded-Bold.woff

1660 ms

MohrRounded-Heavy.woff

MohrRounded-Heavy.woff

1306 ms

MohrRounded-Black.woff

MohrRounded-Black.woff

1654 ms

wp-polyfill-fetch.min.js

wp-polyfill-fetch.min.js

1189 ms

wp-polyfill-dom-rect.min.js

wp-polyfill-dom-rect.min.js

1214 ms

wp-polyfill-url.min.js

wp-polyfill-url.min.js

1214 ms

wp-polyfill-formdata.min.js

wp-polyfill-formdata.min.js

1539 ms

wp-polyfill-element-closest.min.js

wp-polyfill-element-closest.min.js

1283 ms

wp-polyfill-object-fit.min.js

wp-polyfill-object-fit.min.js

1545 ms

logo.svg

logo.svg

1529 ms

picturefill.min.js

picturefill.min.js

418 ms

Accessibility Review

enlaze.net accessibility score

89

Accessibility Issues

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Best Practices

enlaze.net best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

enlaze.net SEO score

87

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

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Enlaze.net can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and it matches the claimed language. Our system also found out that Enlaze.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

enlaze.net

Open Graph data is detected on the main page of En La Ze. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: