Access aesp.org. AESP / Cultivating A Community of Clean Energy Professionals

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

67/100

25%

SI (Speed Index)

Value6.9 s

33/100

10%

TBT (Total Blocking Time)

Value380 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.319

36/100

15%

TTI (Time to Interactive)

Value16.7 s

5/100

10%

aesp.org

156 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

42 ms

Our browser made a total of 2 requests to load all elements on the main page. We found that 50% of them (1 request) were addressed to the original Aesp.org, 50% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (156 ms) belongs to the original domain Aesp.org.

Content Size

568.8 kB

After Optimization

545.2 kB

In fact, the total size of Aesp.org main page is 568.8 kB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 517.9 kB which makes up the majority of the site volume.

HTML Optimization

-32%

Potential reduce by 225 B

Original 711 B
After minification 711 B
After compression 486 B

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 225 B or 32% of the original size.

Image Optimization

-3%

Potential reduce by 16.8 kB

Original 517.9 kB
After minification 501.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. AESP images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 5.6 kB

Original 42.9 kB
After minification 42.9 kB
After compression 37.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 5.6 kB or 13% of the original size.

CSS Optimization

-13%

Potential reduce by 974 B

Original 7.3 kB
After minification 7.3 kB
After compression 6.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. Aesp.org needs all CSS files to be minified and compressed as it can save up to 974 B or 13% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

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

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

These items highlight common accessibility best practices.

High

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

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

Search Engine Optimization Advices

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

High

Links do not have descriptive text

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

EN
Language Claimed

N/A
Encoding

N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aesp.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Aesp.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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