3.5 sec in total
535 ms
2.7 sec
299 ms
Welcome to yashilvatan.ir homepage info - get ready to check Yashilvatan best content for Iran right away, or after learning these important things about yashilvatan.ir
Visit yashilvatan.irWe analyzed Yashilvatan.ir page load time and found that the first response time was 535 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
yashilvatan.ir performance score
name
value
score
weighting
Value6.6 s
2/100
10%
Value6.9 s
7/100
25%
Value11.6 s
4/100
10%
Value800 ms
36/100
30%
Value0.003
100/100
15%
Value12.4 s
15/100
10%
535 ms
215 ms
234 ms
237 ms
236 ms
Our browser made a total of 91 requests to load all elements on the main page. We found that 82% of them (75 requests) were addressed to the original Yashilvatan.ir, 8% (7 requests) were made to 0.gravatar.com and 4% (4 requests) were made to 2.gravatar.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Yashilvatan.ir.
Page size can be reduced by 461.3 kB (49%)
937.7 kB
476.4 kB
In fact, the total size of Yashilvatan.ir main page is 937.7 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. 45% of websites need less resources to load. Images take 404.0 kB which makes up the majority of the site volume.
Potential reduce by 103.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 103.7 kB or 87% of the original size.
Potential reduce by 42.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. Yashilvatan images are well optimized though.
Potential reduce by 166.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 166.1 kB or 70% of the original size.
Potential reduce by 149.1 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. Yashilvatan.ir needs all CSS files to be minified and compressed as it can save up to 149.1 kB or 83% of the original size.
Number of requests can be reduced by 27 (31%)
88
61
The browser has sent 88 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Yashilvatan. 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 8 to 1 for CSS and as a result speed up the page load time.
yashilvatan.ir
535 ms
wp-emoji-release.min.js
215 ms
wti_like_post.css
234 ms
polls-css.css
237 ms
polls-css-rtl.css
236 ms
style.css
365 ms
css
25 ms
wpp.css
240 ms
thickbox.min.css
331 ms
jquery.js
469 ms
jquery-migrate.min.js
351 ms
wti_like_post.js
351 ms
thickbox.min.js
363 ms
rtl.css
449 ms
c.aspx
150 ms
polls-js.js
374 ms
tie-scripts.js
492 ms
wp-embed.min.js
431 ms
5fe4e05eda63c9c5f81fdeef1fb2e092
66 ms
9d4d0f5030fa40e5c4933f7f2bd10b0c
65 ms
d268063a32940f2ed463f9969e84af8b
65 ms
8d7391a5bbd80c5adf4eaa4c973d31c4
86 ms
e43b3b0cee40ff84d34bc541c8078418
406 ms
5d09f4cd725ffe7820e1c12592d735fa
407 ms
0c402f047365720dbcd66314565a0e51
83 ms
f437acfbd1a20435cf070938bb854713
405 ms
9277f23f9c1d9b6ee32c8a93c451831e
404 ms
c0bfa2d5e13a7a764b46da21a90154af
405 ms
634d694044d426a375e37918b86182e6
406 ms
cfec98750a72487e6f463a93b44bda8d
406 ms
Untitled-2-e1430642418600.png
408 ms
Hasannn_0061-300x160.jpg
407 ms
photo_2016-02-06_23-53-26-1-70x70.jpg
408 ms
Capture-44-70x70.jpg
409 ms
Capture-40-70x70.jpg
406 ms
Capture-37-70x70.jpg
411 ms
A0900070-70x70.jpg
442 ms
Capture-47-70x70.jpg
442 ms
%D8%B9%DA%A9%D8%B3-%D8%AE%D8%A8%D8%B1-70x70.jpg
443 ms
Capture-43-70x70.jpg
441 ms
Capture-42-70x70.jpg
441 ms
photo_2016-02-25_08-38-07-70x70.jpg
442 ms
Capture-36-70x70.jpg
545 ms
images-22-70x70.jpg
530 ms
Capture-38-70x70.jpg
531 ms
images-70x70.jpg
545 ms
%D8%A7%D8%B7%D9%84%D8%A7%D8%B9%DB%8C%D9%87-%DB%8C%D8%A7%D8%B4%DB%8C%D9%84-%D9%88%D8%B7%D9%862-70x70.jpg
546 ms
photo_2016-02-23_11-09-16-70x70.jpg
530 ms
Capture-34-70x70.jpg
655 ms
%D8%AC%D8%A7%D9%84%D8%A8-%DB%8C%D8%A7%D8%B4%DB%8C%D9%84-%D9%88%D8%B7%D9%86-70x70.jpg
654 ms
Capture-33-70x70.jpg
654 ms
Capture-32-70x70.jpg
656 ms
photo_2016-02-23_00-10-47-70x70.jpg
657 ms
photo_2016-02-21_13-50-44-70x70.jpg
657 ms
photo_2016-02-21_12-25-07-70x70.jpg
762 ms
20150114161734297-70x70.jpg
763 ms
photo_2016-02-20_19-17-18-70x70.jpg
763 ms
Capture-31-70x70.jpg
771 ms
%D8%A7%D9%86%D8%AA%D8%AE%D8%A7%D8%A8%D8%A7%D8%AA-70x70.jpg
771 ms
DSC_0033-70x70.jpg
783 ms
download-4-1-70x70.jpg
881 ms
%D8%B1%D8%AD%D9%85%D8%A7%D9%86-%D8%B9%D8%A8%D8%A7%D8%B3%DB%8C-70x70.jpg
882 ms
photo_2016-02-18_21-25-39-70x70.jpg
883 ms
SAM_0311-252x3001-70x70.jpg
876 ms
tiefontello.svg
880 ms
printfriendly.js
328 ms
1f4a0.png
355 ms
tiefontello.woff
630 ms
DroidNaskh-Regular.woff
830 ms
A6-70x70.jpg
596 ms
Capture-30-70x70.jpg
597 ms
photo_2016-02-06_23-53-26-70x70.jpg
599 ms
Capture1-70x70.jpg
618 ms
photo_2016-02-17_13-04-27-70x70.jpg
693 ms
ImageHandler-22-70x70.jpg
680 ms
emamj-70x70.jpg
682 ms
images-1-70x70.jpg
696 ms
download-70x70.jpg
700 ms
Hasannn_0061-70x70.jpg
794 ms
Capture.JPG2_-300x160.jpg
828 ms
%D8%BA%D8%BA%D8%BA%D8%BA-300x160.jpg
769 ms
n00283579-b-275x160.jpg
769 ms
c54ef813_81f5_4786_b408_7fc16b7206a1-300x160.jpg
758 ms
IMAGE635819663296763545-300x160.jpg
809 ms
Capture-34-300x160.jpg
809 ms
Capture-31-300x160.jpg
793 ms
Capture-28-300x160.jpg
719 ms
Capture-18-293x160.jpg
847 ms
header.jpg
1080 ms
top-shadow.png
805 ms
black-loader.gif
815 ms
yashilvatan.ir accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
yashilvatan.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
yashilvatan.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
FA
FA
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yashilvatan.ir 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 Yashilvatan.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.
yashilvatan.ir
Open Graph description is not detected on the main page of Yashilvatan. 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: