Access navaar.ir.

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.4 s

83/100

10%

navaar.ir

395 ms

www.navaar.ir

1123 ms

css

496 ms

jquery.min.js

31 ms

angularjs

538 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 83% of them (70 requests) were addressed to the original Navaar.ir, 4% (3 requests) were made to V2.zopim.com and 2% (2 requests) were made to S7.addthis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Trustseal.enamad.ir.

Content Size

1.5 MB

After Optimization

957.0 kB

In fact, the total size of Navaar.ir main page is 1.5 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. 70% of websites need less resources to load. Images take 741.8 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 168.8 kB

Original 200.5 kB
After minification 181.2 kB
After compression 31.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 168.8 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 25.5 kB

Original 741.8 kB
After minification 716.3 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. Navaar images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 381.8 kB

Original 590.9 kB
After minification 590.9 kB
After compression 209.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 381.8 kB or 65% of the original size.

Requests Now

After Optimization

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Navaar. 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 as a result speed up the page load time.

Accessibility Issues

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.

High

Buttons do not have an accessible name

High

Links do not have a discernible name

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

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

High

Browser errors were logged to the console

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

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

FA
Language Claimed

EN
Encoding

UTF-8

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

navaar.ir

Open Graph data is detected on the main page of Navaar. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook:

Report Summary

Performance

Accessibility

Best Practices

SEO

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

navaar.ir

www.navaar.ir

css

jquery.min.js

angularjs

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

navaar.ir

www.navaar.ir

css

jquery.min.js

angularjs

js

app

addthis_widget.js

analytics.js

a

logo.aspx

logo-w.png

rasad.png

koodakane-omid-logo.png

telegram.svg

widget_v2.132.js

genres

index.html

BYekanM.woff

glyphicons-halflings-regular.woff

socialicious.ttf

collect

collect

slides

free

trial

latest

editor

bestseller

comingsoon

featured

register2.jpg

app2.jpg

carousel_list.html

bullet.png

pic.jpg

__$$__stringtable_lang_fa.js

pic.jpg

pic.jpg

pic.jpg

pic.jpg

pic.jpg

pic.jpg

pic.jpg

pic.jpg

$$stringtable_lang_fa.js