Report Summary

  • 47

    Performance

    Renders faster than
    65% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

aeenebahai.org

آیین بهایی | تعالیم و عقاید آئین بهائی

Page Load Speed

1.3 sec in total

First Response

61 ms

Resources Loaded

906 ms

Page Rendered

327 ms

About Website

Click here to check amazing Aeenebahai content for United States. Otherwise, check out these important facts you probably never knew about aeenebahai.org

آیین بهایی (بهاییت) چیست؟ سایت آئین بهائی بهاییت سایتی برای معرفی دیانت بهائی به هموطنان عزیز ایرانی و نیز دیگر فارسی زبانان شریف می باشد.

Visit aeenebahai.org

Key Findings

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

Performance Metrics

aeenebahai.org performance score

47

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

45/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

10/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value200 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.815

4/100

15%

TTI (Time to Interactive)

Value7.6 s

47/100

10%

Network Requests Diagram

fa

61 ms

css_1IPY1A8ooBlfDk0A39LbR7mqwp8b5PoaQGUN-oYphbw.css

21 ms

css_ibQP4eERZMUghpcl7J59nIA8odX2TZCQdq9NRb6W19E.css

22 ms

css_7D1rYcp16AVfuuwZkCy3VyMS_84mkuBtmGJ0wM7a0C0.css

23 ms

bootstrap.min.css

33 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 83% of them (24 requests) were addressed to the original Aeenebahai.org, 10% (3 requests) were made to Maxcdn.bootstrapcdn.com and 3% (1 request) were made to Ajax.googleapis.com. The less responsive or slowest element that took the longest time to load (283 ms) relates to the external source Google-analytics.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (81%)

Content Size

2.2 MB

After Optimization

425.9 kB

In fact, the total size of Aeenebahai.org main page is 2.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. 60% of websites need less resources to load. HTML takes 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-94%

Potential reduce by 1.7 MB

  • Original 1.8 MB
  • After minification 1.8 MB
  • After compression 111.0 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 1.7 MB or 94% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 179.4 kB
  • After minification 179.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. Aeenebahai images are well optimized though.

JavaScript Optimization

-12%

Potential reduce by 11.1 kB

  • Original 96.5 kB
  • After minification 95.8 kB
  • After compression 85.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 11.1 kB or 12% of the original size.

CSS Optimization

-68%

Potential reduce by 104.8 kB

  • Original 155.0 kB
  • After minification 143.0 kB
  • After compression 50.1 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. Aeenebahai.org needs all CSS files to be minified and compressed as it can save up to 104.8 kB or 68% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (74%)

Requests Now

27

After Optimization

7

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

Accessibility Review

aeenebahai.org accessibility score

86

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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.

Best Practices

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

aeenebahai.org SEO score

91

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    FA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aeenebahai.org can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and it matches the claimed language. Our system also found out that Aeenebahai.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

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