Tools & Wizards About Us
farshesialk.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

farshesialk.com

بازار فرش سیلک - خرید اینترنتی فرش

Page Load Speed

7.6 sec in total

First Response

1.2 sec

Resources Loaded

5.8 sec

Page Rendered

604 ms

farshesialk.com screenshot

About Website

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

خرید اینترنتی فرش - ارسال رایگان به سراسر کشور

Visit farshesialk.com

Key Findings

We analyzed Farshesialk.com page load time and found that the first response time was 1.2 sec and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster. This domain responded with an error, which can significantly jeopardize Farshesialk.com rating and web reputation

Performance Metrics

farshesialk.com performance score

0

Network Requests Diagram

farshesialk.com

1172 ms

foundation.css

707 ms

responsiv-horizantal.css

477 ms

slick.css

465 ms

slick-theme.css

488 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 99% of them (74 requests) were addressed to the original Farshesialk.com, 1% (1 request) were made to Trustseal.enamad.ir. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Farshesialk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 513.7 kB (22%)

Content Size

2.3 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Farshesialk.com main page is 2.3 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. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 67.7 kB

  • Original 80.2 kB
  • After minification 59.1 kB
  • After compression 12.5 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. This page needs HTML code to be minified as it can gain 21.1 kB, which is 26% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 67.7 kB or 84% of the original size.

Image Optimization

-1%

Potential reduce by 21.6 kB

  • Original 1.7 MB
  • After minification 1.7 MB

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. Farshesialk images are well optimized though.

JavaScript Optimization

-73%

Potential reduce by 214.4 kB

  • Original 293.7 kB
  • After minification 277.6 kB
  • After compression 79.3 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 214.4 kB or 73% of the original size.

CSS Optimization

-86%

Potential reduce by 210.0 kB

  • Original 244.9 kB
  • After minification 227.0 kB
  • After compression 34.8 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. Farshesialk.com needs all CSS files to be minified and compressed as it can save up to 210.0 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (37%)

Requests Now

68

After Optimization

43

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

farshesialk.com

farshesialk.com

1172 ms

foundation.css

foundation.css

707 ms

responsiv-horizantal.css

responsiv-horizantal.css

477 ms

slick.css

slick.css

465 ms

slick-theme.css

slick-theme.css

488 ms

style.css

style.css

485 ms

flipclock.css

flipclock.css

454 ms

icons.css

icons.css

927 ms

ion.rangeSlider.css

ion.rangeSlider.css

724 ms

ion.rangeSlider.skinFlat.css

ion.rangeSlider.skinFlat.css

727 ms

slippry.css

slippry.css

725 ms

owl.carousel.css

owl.carousel.css

736 ms

WebResource.axd

WebResource.axd

909 ms

ScriptResource.axd

ScriptResource.axd

1285 ms

ScriptResource.axd

ScriptResource.axd

869 ms

WebResource.axd

WebResource.axd

739 ms

jquery.min.js

jquery.min.js

1318 ms

persianumber.min.js

persianumber.min.js

939 ms

foundation.min.js

foundation.min.js

1199 ms

modernizr.js

modernizr.js

972 ms

slick.min.js

slick.min.js

1077 ms

responsiveCarousel.min.js

responsiveCarousel.min.js

1190 ms

flipclock.min.js

flipclock.min.js

1196 ms

logo.aspx

logo.aspx

1084 ms

logo.jpg

logo.jpg

790 ms

model.jpg

model.jpg

1481 ms

model2.jpg

model2.jpg

1057 ms

model3.png

model3.png

1109 ms

1.jpg

1.jpg

1512 ms

2.jpg

2.jpg

1549 ms

3.jpg

3.jpg

1965 ms

tik.png

tik.png

1242 ms

seven.png

seven.png

1363 ms

dolor.png

dolor.png

1465 ms

car.png

car.png

1626 ms

example3.jpg

example3.jpg

2311 ms

example2.jpg

example2.jpg

1729 ms

example.jpg

example.jpg

2155 ms

3138.jpg

3138.jpg

1789 ms

3035.jpg

3035.jpg

1879 ms

3139.jpg

3139.jpg

1947 ms

4039.jpg

4039.jpg

2016 ms

4092.jpg

4092.jpg

2159 ms

3160.jpg

3160.jpg

2236 ms

3038.jpg

3038.jpg

2181 ms

4077.jpg

4077.jpg

2284 ms

3118.jpg

3118.jpg

2426 ms

3078.jpg

3078.jpg

2413 ms

4121.jpg

4121.jpg

2404 ms

4120.jpg

4120.jpg

2458 ms

4119.jpg

4119.jpg

2534 ms

4118.jpg

4118.jpg

2408 ms

4117.jpg

4117.jpg

2448 ms

4116.jpg

4116.jpg

2428 ms

4115.jpg

4115.jpg

2354 ms

4114.jpg

4114.jpg

2232 ms

4113.jpg

4113.jpg

2334 ms

4112.jpg

4112.jpg

2351 ms

1015.jpg

1015.jpg

2324 ms

view.png

view.png

2231 ms

Yekan.woff

Yekan.woff

2163 ms

icons.woff

icons.woff

2166 ms

slick.woff

slick.woff

2024 ms

news.png

news.png

1891 ms

1009.jpg

1009.jpg

1808 ms

yalda.png

yalda.png

1700 ms

ghitaran.png

ghitaran.png

1886 ms

khoob.png

khoob.png

1869 ms

previous.png

previous.png

1821 ms

next.png

next.png

1817 ms

ajax-loader.gif

ajax-loader.gif

1652 ms

big-prev.png

big-prev.png

1676 ms

big-next.png

big-next.png

1740 ms

slick.ttf

slick.ttf

420 ms

slick.svg

slick.svg

213 ms

SEO Factors

farshesialk.com SEO score

0

Language and Encoding

  • Language Detected

    FA

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Farshesialk.com can be misinterpreted by Google and other search engines. Our service has detected that Persian is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Farshesialk.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

farshesialk.com

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