Tools & Wizards About Us
a8e.org screenshot

Report Summary

  • 76

    Performance

    Renders faster than
    84% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

a8e.org

SCHLIX - Free CMS, blog and website builder (open source) for PHP/MySQL

Page Load Speed

2.5 sec in total

First Response

845 ms

Resources Loaded

1.3 sec

Page Rendered

371 ms

a8e.org screenshot

About Website

Welcome to a8e.org homepage info - get ready to check A 8 E best content right away, or after learning these important things about a8e.org

SCHLIX CMS - extensible and high performance CMS, blog and web builder written in PHP/MySQL - open source, free

Visit a8e.org

Key Findings

We analyzed A8e.org page load time and found that the first response time was 845 ms and then it took 1.6 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

a8e.org performance score

76

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

28/100

25%

SI (Speed Index)

Value2.9 s

94/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.6 s

91/100

10%

Network Requests Diagram

a8e.org

845 ms

www.schlix.com

153 ms

font-awesome.min.css

19 ms

extra.css

35 ms

bootstrap.min.css

70 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original A8e.org, 94% (31 requests) were made to Schlix.com and 3% (1 request) were made to R.schlix.com. The less responsive or slowest element that took the longest time to load (845 ms) belongs to the original domain A8e.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 31.6 kB (5%)

Content Size

666.5 kB

After Optimization

634.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of A8e.org main page is 666.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. Images take 530.2 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 12.8 kB

  • Original 17.4 kB
  • After minification 15.2 kB
  • After compression 4.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 2.2 kB, which is 13% 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 12.8 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 15.8 kB

  • Original 530.2 kB
  • After minification 514.4 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. A 8 E images are well optimized though.

JavaScript Optimization

-4%

Potential reduce by 2.6 kB

  • Original 70.0 kB
  • After minification 68.7 kB
  • After compression 67.4 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

-1%

Potential reduce by 385 B

  • Original 48.9 kB
  • After minification 48.9 kB
  • After compression 48.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. A8e.org has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (30%)

Requests Now

27

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

a8e.org

a8e.org

845 ms

www.schlix.com

www.schlix.com

153 ms

font-awesome.min.css

font-awesome.min.css

19 ms

extra.css

extra.css

35 ms

bootstrap.min.css

bootstrap.min.css

70 ms

style2021.min.css

style2021.min.css

47 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

76 ms

bootstrap.min.js

bootstrap.min.js

50 ms

bootstrap-submenu.js

bootstrap-submenu.js

47 ms

schlix.js

schlix.js

48 ms

schlix_darkbg_logo_v2_48.png

schlix_darkbg_logo_v2_48.png

61 ms

schlix_darkbg_logo_v2_32.png

schlix_darkbg_logo_v2_32.png

62 ms

schlix_cms_v22_screenshot_main.jpg

schlix_cms_v22_screenshot_main.jpg

100 ms

schlix_v22_sample_2.jpg

schlix_v22_sample_2.jpg

99 ms

schlix_utf8_seo_url.png

schlix_utf8_seo_url.png

78 ms

schlix_sample_6.jpg

schlix_sample_6.jpg

106 ms

schlix_v22_sample_12.jpg

schlix_v22_sample_12.jpg

111 ms

logo_softaculous.png

logo_softaculous.png

86 ms

logo_fantastico_f3.png

logo_fantastico_f3.png

98 ms

logo_odin_sa.png

logo_odin_sa.png

102 ms

logo_plesk.png

logo_plesk.png

113 ms

aws_marketplace_logo.png

aws_marketplace_logo.png

114 ms

logo_mswebapp.png

logo_mswebapp.png

115 ms

logo_docker.png

logo_docker.png

119 ms

ttr.png

ttr.png

121 ms

fontawesome-all.min.css

fontawesome-all.min.css

111 ms

j

j

113 ms

schlix2021.jpg

schlix2021.jpg

49 ms

carbon.png

carbon.png

16 ms

fa-solid-900.woff

fa-solid-900.woff

62 ms

fa-regular-400.woff

fa-regular-400.woff

51 ms

lato-v16-latin-700.woff

lato-v16-latin-700.woff

22 ms

lato-v16-latin-regular.woff

lato-v16-latin-regular.woff

26 ms

Accessibility Review

a8e.org accessibility score

95

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

a8e.org best practices score

75

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

a8e.org SEO score

100

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

a8e.org

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