Access saresh.org. بازرگانی صارش - واردات کالا، ثبت سفارش و ترخیص کالا

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value3.0 s

79/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value130 ms

96/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value3.3 s

94/100

10%

saresh.org

720 ms

MP_Slider_1_c.jpg

997 ms

MP_Slider_2_ccc.jpg

1066 ms

MP_Slider_3.jpg

873 ms

MP_Slider_4.jpg

1112 ms

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

Content Size

772.4 kB

After Optimization

636.4 kB

In fact, the total size of Saresh.org main page is 772.4 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. 20% of websites need less resources to load. Images take 618.6 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 124.8 kB

Original 153.8 kB
After minification 153.4 kB
After compression 29.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 124.8 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 11.2 kB

Original 618.6 kB
After minification 607.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. Saresh images are well optimized though.

Requests Now

After Optimization

The browser has sent 14 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Saresh. According to our analytics all requests are already optimized.

Accessibility Issues

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.

High

button, link, and menuitem elements do not have accessible names.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

Low

Detected JavaScript libraries

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

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