6.8 sec in total
1.1 sec
5.5 sec
197 ms
Visit ijhoscr.tums.ac.ir now to see the best up-to-date Ijhoscr Tums content for Iran and also check out these interesting facts you probably never knew about ijhoscr.tums.ac.ir
Visit ijhoscr.tums.ac.irWe analyzed Ijhoscr.tums.ac.ir page load time and found that the first response time was 1.1 sec and then it took 5.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
ijhoscr.tums.ac.ir performance score
name
value
score
weighting
Value4.0 s
23/100
10%
Value5.6 s
18/100
25%
Value11.2 s
5/100
10%
Value520 ms
56/100
30%
Value0.012
100/100
15%
Value13.0 s
12/100
10%
1066 ms
358 ms
365 ms
368 ms
545 ms
Our browser made a total of 55 requests to load all elements on the main page. We found that 91% of them (50 requests) were addressed to the original Ijhoscr.tums.ac.ir, 4% (2 requests) were made to Ajax.googleapis.com and 2% (1 request) were made to Google.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Ijhoscr.tums.ac.ir.
Page size can be reduced by 402.7 kB (72%)
556.5 kB
153.8 kB
In fact, the total size of Ijhoscr.tums.ac.ir main page is 556.5 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. Images take 228.1 kB which makes up the majority of the site volume.
Potential reduce by 20.8 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 20.8 kB or 79% of the original size.
Potential reduce by 123.7 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. Obviously, Ijhoscr Tums needs image optimization as it can save up to 123.7 kB or 54% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 174.9 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 174.9 kB or 87% of the original size.
Potential reduce by 83.3 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. Ijhoscr.tums.ac.ir needs all CSS files to be minified and compressed as it can save up to 83.3 kB or 83% of the original size.
Number of requests can be reduced by 36 (68%)
53
17
The browser has sent 53 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ijhoscr Tums. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 27 to 1 for JavaScripts and from 11 to 1 for CSS and as a result speed up the page load time.
ijhoscr
1066 ms
pkp.css
358 ms
common.css
365 ms
common.css
368 ms
compiled.css
545 ms
jsapi
27 ms
sidebar.css
373 ms
leftSidebar.css
635 ms
rightSidebar.css
709 ms
bothSidebars.css
720 ms
ddmenu.css
724 ms
jquery.tag-it.js
732 ms
jquery.cookie.js
902 ms
fontController.js
995 ms
general.js
1069 ms
jqueryValidatorI18n.js
1080 ms
Helper.js
1084 ms
ObjectProxy.js
1095 ms
Handler.js
1443 ms
LinkActionRequest.js
1355 ms
Feature.js
1427 ms
SiteHandler.js
1434 ms
UrlInDivHandler.js
1443 ms
AutocompleteHandler.js
1456 ms
ExtrasOnDemandHandler.js
1716 ms
FormHandler.js
1781 ms
AjaxFormHandler.js
1793 ms
ClientFormHandler.js
1793 ms
GridHandler.js
1980 ms
LinkActionHandler.js
1839 ms
SearchFormHandler.js
2084 ms
ReportGeneratorFormHandler.js
2325 ms
LuceneAutocompleteHandler.js
2153 ms
jquery.pkp.js
2163 ms
jquery.validate.js
2597 ms
jqueryUi.css
2184 ms
jquery.pnotify.default.css
2102 ms
jquery.min.js
29 ms
jquery-ui.min.js
59 ms
bkg11.jpg
559 ms
jhheadertop.jpg
543 ms
elmerpressheader20.jpg
539 ms
leftbg20.jpg
582 ms
leftbarimg.jpg
544 ms
homepageImage_en_US.jpg
366 ms
PDF.png
730 ms
XML.png
894 ms
mnu.png
794 ms
jhfooter1.jpg
1070 ms
page.gif
850 ms
titleblock.jpg
1034 ms
font-down.png
888 ms
font-default.png
1035 ms
font-up.png
1202 ms
88x31.png
41 ms
ijhoscr.tums.ac.ir accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
Image elements do not have [alt] attributes
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
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
ijhoscr.tums.ac.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
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
ijhoscr.tums.ac.ir SEO score
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ijhoscr.tums.ac.ir can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Ijhoscr.tums.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.
ijhoscr.tums.ac.ir
Open Graph description is not detected on the main page of Ijhoscr Tums. 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: