Tools & Wizards About Us

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

aggreko.es

Aggreko Home | Aggreko ES

Page Load Speed

5.4 sec in total

First Response

8 ms

Resources Loaded

3.7 sec

Page Rendered

1.7 sec

About Website

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

Aggreko Home

Visit aggreko.es

Key Findings

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

Performance Metrics

aggreko.es performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value6.8 s

7/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value3,050 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.8 s

13/100

10%

Network Requests Diagram

aggreko.es

8 ms

es-es

187 ms

es-es

1446 ms

styles

1206 ms

main-sm.css

31 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Aggreko.es, 48% (33 requests) were made to Bynder.aggreko.com and 17% (12 requests) were made to Aggreko.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Aggreko.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 276.1 kB (20%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Aggreko.es main page is 1.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. 55% of websites need less resources to load. Images take 751.5 kB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 109.2 kB

  • Original 127.0 kB
  • After minification 83.2 kB
  • After compression 17.9 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 43.8 kB, which is 34% 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 109.2 kB or 86% of the original size.

Image Optimization

-5%

Potential reduce by 36.4 kB

  • Original 751.5 kB
  • After minification 715.1 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. Aggreko images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 3.3 kB

  • Original 313.5 kB
  • After minification 313.5 kB
  • After compression 310.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. This website has mostly compressed JavaScripts.

CSS Optimization

-81%

Potential reduce by 127.3 kB

  • Original 157.8 kB
  • After minification 157.8 kB
  • After compression 30.5 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. Aggreko.es needs all CSS files to be minified and compressed as it can save up to 127.3 kB or 81% of the original size.

Requests Breakdown

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

Requests Now

66

After Optimization

39

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

aggreko.es accessibility score

100

Accessibility Issues

Best Practices

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

General

Impact

Issue

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

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

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

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

    ES

  • Language Claimed

    ES

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aggreko.es 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 Aggreko.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 data is detected on the main page of Aggreko. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: