Report Summary

  • 80

    Performance

    Renders faster than
    86% of other websites

  • 53

    Accessibility

    Visual factors better than
    that of 22% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

Page Load Speed

13.4 sec in total

First Response

1.7 sec

Resources Loaded

4.1 sec

Page Rendered

7.5 sec

ayenda.org screenshot

About Website

Visit ayenda.org now to see the best up-to-date Ayenda content for Afghanistan and also check out these interesting facts you probably never knew about ayenda.org

Visit ayenda.org

Key Findings

We analyzed Ayenda.org page load time and found that the first response time was 1.7 sec and then it took 11.6 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

ayenda.org performance score

80

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

69/100

25%

SI (Speed Index)

Value2.9 s

94/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.207

60/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

ayenda.org

1747 ms

Enwan4.jpg

559 ms

Safhe%20Ekhtesasi.jpg

367 ms

Etelaf%20Ahzab2.jpg

367 ms

Etelaf.JPG

207 ms

Our browser made a total of 133 requests to load all elements on the main page. We found that 83% of them (110 requests) were addressed to the original Ayenda.org, 5% (7 requests) were made to Cdn.livestream.com and 5% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Ayenda.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (24%)

Content Size

5.3 MB

After Optimization

4.1 MB

In fact, the total size of Ayenda.org main page is 5.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. 80% 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 4.3 MB which makes up the majority of the site volume.

HTML Optimization

-86%

Potential reduce by 441.9 kB

  • Original 514.6 kB
  • After minification 475.9 kB
  • After compression 72.7 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 441.9 kB or 86% of the original size.

Image Optimization

-11%

Potential reduce by 473.6 kB

  • Original 4.3 MB
  • After minification 3.9 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. Obviously, Ayenda needs image optimization as it can save up to 473.6 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 159.1 kB

  • Original 239.5 kB
  • After minification 238.5 kB
  • After compression 80.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 159.1 kB or 66% of the original size.

CSS Optimization

-83%

Potential reduce by 206.2 kB

  • Original 249.8 kB
  • After minification 249.7 kB
  • After compression 43.6 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. Ayenda.org needs all CSS files to be minified and compressed as it can save up to 206.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 6 (5%)

Requests Now

119

After Optimization

113

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

Accessibility Review

ayenda.org accessibility score

53

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.

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

<frame> or <iframe> elements do not have a title

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

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

ayenda.org best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

ayenda.org SEO score

92

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    DE

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ayenda.org can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it does not match the claimed German language. Our system also found out that Ayenda.org main page’s claimed encoding is windows-1252. 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 Ayenda. 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: