Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 77

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

eslahe.com

نوگرا,نوگرا

Page Load Speed

26 sec in total

First Response

9.9 sec

Resources Loaded

15.4 sec

Page Rendered

741 ms

eslahe.com screenshot

About Website

Click here to check amazing Eslahe content for Iran. Otherwise, check out these important facts you probably never knew about eslahe.com

نوگرا سایتی برای نواندیشان

Visit eslahe.com

Key Findings

We analyzed Eslahe.com page load time and found that the first response time was 9.9 sec and then it took 16.1 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

eslahe.com performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

30/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

4/100

25%

SI (Speed Index)

Value5.6 s

53/100

10%

TBT (Total Blocking Time)

Value630 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.105

89/100

15%

TTI (Time to Interactive)

Value6.3 s

61/100

10%

Network Requests Diagram

eslahe.com

9918 ms

fonts.css

161 ms

style.css

181 ms

dashicons.min.css

244 ms

desktop_style.css

181 ms

Our browser made a total of 182 requests to load all elements on the main page. We found that 97% of them (177 requests) were addressed to the original Eslahe.com, 1% (2 requests) were made to Css.rating-widget.com and 1% (2 requests) were made to S.w.org. The less responsive or slowest element that took the longest time to load (9.9 sec) belongs to the original domain Eslahe.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 857.0 kB (42%)

Content Size

2.1 MB

After Optimization

1.2 MB

In fact, the total size of Eslahe.com main page is 2.1 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. 65% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 245.4 kB

  • Original 293.7 kB
  • After minification 278.6 kB
  • After compression 48.4 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 245.4 kB or 84% of the original size.

Image Optimization

-6%

Potential reduce by 59.3 kB

  • Original 1.0 MB
  • After minification 954.9 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. Eslahe images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 302.3 kB

  • Original 421.3 kB
  • After minification 376.4 kB
  • After compression 119.1 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 302.3 kB or 72% of the original size.

CSS Optimization

-77%

Potential reduce by 250.0 kB

  • Original 323.1 kB
  • After minification 268.4 kB
  • After compression 73.0 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. Eslahe.com needs all CSS files to be minified and compressed as it can save up to 250.0 kB or 77% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (23%)

Requests Now

176

After Optimization

136

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

Accessibility Review

eslahe.com accessibility score

68

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

[aria-hidden="true"] elements contain focusable descendents

High

ARIA input fields do not have accessible names

High

[aria-*] attributes do not have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

eslahe.com best practices score

77

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

Browser errors were logged to the console

SEO Factors

eslahe.com SEO score

77

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Eslahe.com 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 Eslahe.com 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 Eslahe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: