Tools & Wizards About Us
nrskh.ir screenshot

Report Summary

  • 6

    Performance

    Renders faster than
    21% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 43% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 85

    SEO

    Google-friendlier than
    56% of websites

nrskh.ir

Page Load Speed

4.3 sec in total

First Response

689 ms

Resources Loaded

2.9 sec

Page Rendered

723 ms

nrskh.ir screenshot

About Website

Click here to check amazing Nrskh content for Iran. Otherwise, check out these important facts you probably never knew about nrskh.ir

اداره کل منابع طبیعی و آبخیزداری خراسان جنوبی

Visit nrskh.ir

Key Findings

We analyzed Nrskh.ir page load time and found that the first response time was 689 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

nrskh.ir performance score

6

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value16.3 s

0/100

25%

SI (Speed Index)

Value15.8 s

0/100

10%

TBT (Total Blocking Time)

Value1,470 ms

14/100

30%

CLS (Cumulative Layout Shift)

Value1.165

1/100

15%

TTI (Time to Interactive)

Value15.8 s

6/100

10%

Network Requests Diagram

nrskh.ir

689 ms

415b291711679e398cc09a94caa2fc52.css

197 ms

defafb7bece29dbacae4ab3b1bb05186.css

388 ms

6d08662ac213fda5d39beb74e914eb5b.css

439 ms

ca922af0fdcfae04e722e3cc8f999d96.css

586 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that all of those requests were addressed to Nrskh.ir and no external sources were called. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Nrskh.ir.

Page Optimization Overview & Recommendations

Page size can be reduced by 62.7 kB (52%)

Content Size

120.3 kB

After Optimization

57.6 kB

  • HTML
  • Images

In fact, the total size of Nrskh.ir main page is 120.3 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. 40% of websites need less resources to load. HTML takes 76.4 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 62.7 kB

  • Original 76.4 kB
  • After minification 76.2 kB
  • After compression 13.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 62.7 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 1 B

  • Original 43.9 kB
  • After minification 43.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. Nrskh images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 18 (60%)

Requests Now

30

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nrskh.ir

nrskh.ir

689 ms

415b291711679e398cc09a94caa2fc52.css

415b291711679e398cc09a94caa2fc52.css

197 ms

defafb7bece29dbacae4ab3b1bb05186.css

defafb7bece29dbacae4ab3b1bb05186.css

388 ms

6d08662ac213fda5d39beb74e914eb5b.css

6d08662ac213fda5d39beb74e914eb5b.css

439 ms

ca922af0fdcfae04e722e3cc8f999d96.css

ca922af0fdcfae04e722e3cc8f999d96.css

586 ms

a4f9ebc80d10be3611763269fe3c96dd.css

a4f9ebc80d10be3611763269fe3c96dd.css

394 ms

4c53c335838162004e98c77f2a75780a.js

4c53c335838162004e98c77f2a75780a.js

795 ms

d516d9cc7d42927081c13a60ee68f49c.js

d516d9cc7d42927081c13a60ee68f49c.js

603 ms

9486d17ff63332dcef71ce7eae29d10b.js

9486d17ff63332dcef71ce7eae29d10b.js

1160 ms

3023d75086da0e48a2a4165e121dc0c4.js

3023d75086da0e48a2a4165e121dc0c4.js

990 ms

88714468a09de6f0a6de56bcfab7fe6e.js

88714468a09de6f0a6de56bcfab7fe6e.js

627 ms

57b92b98791135d01130d8d1a866ba9b.js

57b92b98791135d01130d8d1a866ba9b.js

786 ms

692deb87215e676a731f7de0eb06bf03.js

692deb87215e676a731f7de0eb06bf03.js

801 ms

_all.css

_all.css

416 ms

_all.css

_all.css

548 ms

_all.css

_all.css

555 ms

_all.css

_all.css

566 ms

polaris.css

polaris.css

616 ms

futurico.css

futurico.css

821 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

289 ms

body-bg4.png

body-bg4.png

282 ms

logo-nr.png

logo-nr.png

281 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

641 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

641 ms

BebasNeue-webfont.woff

BebasNeue-webfont.woff

253 ms

stripe.png

stripe.png

621 ms

wpyar-BTraffic.woff

wpyar-BTraffic.woff

565 ms

wpyar-BYekan.woff

wpyar-BYekan.woff

566 ms

fontello.svg

fontello.svg

373 ms

fontello.woff

fontello.woff

373 ms

lazyload.1.0.2.min.js

lazyload.1.0.2.min.js

205 ms

Accessibility Review

nrskh.ir accessibility score

76

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 input fields do not have accessible names

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

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

nrskh.ir 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

Missing source maps for large first-party JavaScript

SEO Factors

nrskh.ir SEO score

85

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    FA

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Nrskh.ir can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Persian. Our system also found out that Nrskh.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

nrskh.ir

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