7.8 sec in total
2.9 sec
4.7 sec
272 ms
Welcome to ssrc.ac.ir homepage info - get ready to check Ssrc best content for Iran right away, or after learning these important things about ssrc.ac.ir
پژوهشگاه تربیت بدنی وعلوم ورزشی
Visit ssrc.ac.irWe analyzed Ssrc.ac.ir page load time and found that the first response time was 2.9 sec and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
ssrc.ac.ir performance score
name
value
score
weighting
Value3.2 s
43/100
10%
Value3.7 s
59/100
25%
Value12.0 s
4/100
10%
Value1,740 ms
10/100
30%
Value0.499
16/100
15%
Value12.5 s
14/100
10%
2878 ms
354 ms
539 ms
541 ms
24 ms
Our browser made a total of 52 requests to load all elements on the main page. We found that 96% of them (50 requests) were addressed to the original Ssrc.ac.ir, 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.9 sec) belongs to the original domain Ssrc.ac.ir.
Page size can be reduced by 790.7 kB (54%)
1.5 MB
666.3 kB
In fact, the total size of Ssrc.ac.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. 20% of websites need less resources to load. HTML takes 623.4 kB which makes up the majority of the site volume.
Potential reduce by 556.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. 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 556.5 kB or 89% of the original size.
Potential reduce by 56.2 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. Ssrc images are well optimized though.
Potential reduce by 166.7 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.7 kB or 69% of the original size.
Potential reduce by 11.4 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. Ssrc.ac.ir needs all CSS files to be minified and compressed as it can save up to 11.4 kB or 80% of the original size.
Number of requests can be reduced by 32 (63%)
51
19
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ssrc. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
ssrc.ac.ir
2878 ms
GetCSS.aspx
354 ms
fireStyle.css
539 ms
StyleSheet.css
541 ms
ga.js
24 ms
__utm.gif
26 ms
bodybg.jpg
182 ms
WebResource.axd
383 ms
skmmenu.js
548 ms
ScriptResource.axd
558 ms
ScriptResource.axd
749 ms
mail.png
396 ms
home.png
566 ms
en.png
577 ms
winter-94--05-Final-1.jpg.aspx
945 ms
jeld-(1).jpg.aspx
1120 ms
jquery.min.js
770 ms
tabs.js
595 ms
Capturee.aspx
631 ms
Capture-(4).aspx
941 ms
Capture-(2).aspx
1176 ms
Untitled-1.aspx
834 ms
Capture-(7).aspx
954 ms
Capture-(5).aspx
1035 ms
shaa.aspx
1124 ms
Unti.aspx
1638 ms
GetFile.aspx
1146 ms
GetFile.aspx
1238 ms
GetFile.aspx
1478 ms
%D9%85%D8%B9%D8%B1%D9%81%DB%8C-%D8%A8%D8%B1%DA%AF%D8%B2%DB%8C%D8%AF%DA%AF%D8%A7%D9%86-%D9%86%D9%87%D8%A7%DB%8C%DB%8C-%D8%A7%D9%88%D9%84%DB%8C%D9%86-%D9%85%D8%B3%D8%A7%D8%A8%D9%82%D9%87-%D8%A8%DB%8C%D9%86-%D8%A7%D9%84%D9%85%D9%84%D9%84%DB%8C-%D9%BE%DA%98%D9%88%D9%87.aspx
1302 ms
%D8%AA%D9%81%D8%A7%D9%87%D9%85-%D9%86%D8%A7%D9%85%D9%87-%D9%87%D9%85%DA%A9%D8%A7%D8%B1%DB%8C-%D9%85%D8%B4%D8%AA%D8%B1%DA%A9-%D9%85%DB%8C%D8%A7%D9%86-%D9%BE%DA%98%D9%88%D9%87%D8%B4%DA%AF%D8%A7%D9%87-%D8%AA%D8%B1%D8%A8%DB%8C%D8%AA-%D8%A8%D8%AF%D9%86%DB%8C-%D9%88.aspx
1329 ms
%D8%A8%D8%B1%DA%AF%D8%B2%D8%A7%D8%B1%DB%8C-%D8%AC%D9%84%D8%B3%D9%87-%D9%87%D8%B4%D8%AA%D9%85-%D8%B4%D9%88%D8%B1%D8%A7%DB%8C-%D8%B9%D8%A7%D9%84%DB%8C-%D8%B3%DB%8C%D8%A7%D8%B3%D8%AA-%DA%AF%D8%B0%D8%A7%D8%B1%DB%8C-%D9%86%D9%87%D9%85%DB%8C%D9%86-%D9%87%D9%85%D8%A7.aspx
1345 ms
%D8%A7%D9%88%D9%84%DB%8C%D9%86-%D8%B1%D9%88%DB%8C%D8%AF%D8%A7%D8%AF-%D8%A7%DB%8C%D8%AF%D9%87-%D8%A8%D8%A7%D8%B2%D8%A7%D8%B1-%D9%81%D9%86%D8%A7%D9%88%D8%B1%DB%8C-%D9%88-%D8%AA%D8%AC%D9%87%DB%8C%D8%B2%D8%A7%D8%AA-%D9%88%D8%B1%D8%B2%D8%B4%DB%8C-%D8%A8%D8%B1%DA%AF.aspx
1408 ms
%D8%A7%D8%B7%D9%84%D8%A7%D8%B9%DB%8C%D9%87-%D8%AA%D8%BA%DB%8C%DB%8C%D8%B1-%D8%B4%D9%85%D8%A7%D8%B1%D9%87-%D8%AA%D9%85%D8%A7%D8%B3-%D9%87%D8%A7%DB%8C-%D9%BE%DA%98%D9%88%D9%87%D8%B4%DA%AF%D8%A7%D9%87-%D8%AA%D8%B1%D8%A8%DB%8C%D8%AA-%D8%A8%D8%AF%D9%86%DB%8C-%D9%88.aspx
1293 ms
Header.jpg
941 ms
tdrightbg.jpg
959 ms
rightmenubg.jpg
1062 ms
rightmenutop.jpg
1077 ms
rightmenubottom.jpg
1078 ms
rightmenusep.jpg
1121 ms
sidebaxbg.jpg
1138 ms
sidebaxtop.jpg
1234 ms
sidebaxbottom.jpg
1254 ms
boxheader.jpg
1256 ms
topmenubg.jpg
1252 ms
topmenuleft.jpg
1297 ms
topmenuright.jpg
1313 ms
tdleftbg.jpg
1217 ms
teaserbg.jpg
1231 ms
fotter.jpg
1235 ms
tabbg.jpg
1202 ms
GetCSS.aspx
196 ms
ssrc.ac.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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
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.
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
ssrc.ac.ir best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
ssrc.ac.ir SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ssrc.ac.ir 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 Ssrc.ac.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.
ssrc.ac.ir
Open Graph description is not detected on the main page of Ssrc. 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: