Report Summary

  • 3

    Performance

    Renders faster than
    20% of other websites

  • 59

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

prevent.es

Empresa de Cámaras de Seguridad y Videovigilancia | PREVENT

Page Load Speed

6.2 sec in total

First Response

350 ms

Resources Loaded

5.1 sec

Page Rendered

821 ms

prevent.es screenshot

About Website

Visit prevent.es now to see the best up-to-date PREVENT content for Spain and also check out these interesting facts you probably never knew about prevent.es

Prevent Security Systems. Empresa de Seguridad Homologada líder en Videovigilancia, Alarmas y Sistemas de Control de Accesos. Presupuestos sin compromiso.

Visit prevent.es

Key Findings

We analyzed Prevent.es page load time and found that the first response time was 350 ms and then it took 5.9 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

prevent.es performance score

3

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value19.2 s

0/100

25%

SI (Speed Index)

Value15.3 s

1/100

10%

TBT (Total Blocking Time)

Value2,500 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.954

3/100

15%

TTI (Time to Interactive)

Value18.2 s

3/100

10%

Network Requests Diagram

prevent.es

350 ms

www.prevent.es

876 ms

css

59 ms

css

72 ms

font-awesome.min.css

358 ms

Our browser made a total of 140 requests to load all elements on the main page. We found that 55% of them (77 requests) were addressed to the original Prevent.es, 23% (32 requests) were made to Maps.googleapis.com and 6% (9 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Prevent.es.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (22%)

Content Size

5.2 MB

After Optimization

4.1 MB

In fact, the total size of Prevent.es main page is 5.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 3.8 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 90.6 kB

  • Original 108.9 kB
  • After minification 96.4 kB
  • After compression 18.3 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 12.5 kB, which is 11% 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 90.6 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 89.8 kB

  • Original 3.8 MB
  • After minification 3.7 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. PREVENT images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 663.5 kB

  • Original 994.2 kB
  • After minification 941.2 kB
  • After compression 330.8 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 663.5 kB or 67% of the original size.

CSS Optimization

-86%

Potential reduce by 293.6 kB

  • Original 342.9 kB
  • After minification 244.2 kB
  • After compression 49.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. Prevent.es needs all CSS files to be minified and compressed as it can save up to 293.6 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 71 (58%)

Requests Now

123

After Optimization

52

The browser has sent 123 CSS, Javascripts, AJAX and image requests in order to completely render the main page of PREVENT. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.

Accessibility Review

prevent.es accessibility score

59

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

Form elements do not have associated labels

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

prevent.es 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

SEO Factors

prevent.es SEO score

76

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

Links do not have descriptive text

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Prevent.es can be misinterpreted by Google and other search engines. Our service has detected that Spanish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Prevent.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 PREVENT. 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: