40.2 sec in total
1.6 sec
37.6 sec
1 sec
Welcome to classiccard.oghyanoos.ir homepage info - get ready to check Classiccard Oghyanoos best content for Iran right away, or after learning these important things about classiccard.oghyanoos.ir
گالري كلاسيك - پناهي
Visit classiccard.oghyanoos.irWe analyzed Classiccard.oghyanoos.ir page load time and found that the first response time was 1.6 sec and then it took 38.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
classiccard.oghyanoos.ir performance score
1586 ms
14298 ms
1711 ms
5942 ms
2181 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 87% of them (72 requests) were addressed to the original Classiccard.oghyanoos.ir, 11% (9 requests) were made to Oghyanoos.ir and 2% (2 requests) were made to Img7.irna.ir. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Oghyanoos.ir.
Page size can be reduced by 742.4 kB (68%)
1.1 MB
350.8 kB
In fact, the total size of Classiccard.oghyanoos.ir main page is 1.1 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. Javascripts take 490.0 kB which makes up the majority of the site volume.
Potential reduce by 242.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 242.5 kB or 86% of the original size.
Potential reduce by 12.3 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. Classiccard Oghyanoos images are well optimized though.
Potential reduce by 356.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 356.3 kB or 73% of the original size.
Potential reduce by 131.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. Classiccard.oghyanoos.ir needs all CSS files to be minified and compressed as it can save up to 131.3 kB or 91% of the original size.
Number of requests can be reduced by 42 (56%)
75
33
The browser has sent 75 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Classiccard Oghyanoos. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 26 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
classiccard.oghyanoos.ir
1586 ms
company.aspx
14298 ms
animate.css
1711 ms
wow.min.js
5942 ms
prefixfree.js
2181 ms
animate.css
828 ms
skitter.styles.css
271 ms
jquery-1.10.1.min.js
7171 ms
jquery.innerfade.js
548 ms
jquery.lazyload.min.js
601 ms
jquery.easing.1.3.js
723 ms
jquery.skitter.min.js
1294 ms
featurify.min.js
224 ms
payment.js
284 ms
slides.min.jquery.js
1089 ms
jquery.leanModal.min.js
495 ms
oghyanoos_slider.js
943 ms
amenu.js
1177 ms
47018684912796originalcss.css
1544 ms
47018684912796.css
1381 ms
smooth-add.js
2796 ms
WebResource.axd
1819 ms
WebResource.axd
2125 ms
jquery.sticky-kit.min.js
2807 ms
WebResource.axd
4300 ms
ScriptResource.axd
2397 ms
ScriptResource.axd
4271 ms
ScriptResource.axd
4697 ms
jquery.easing.js
2054 ms
jquery.slidorion.min.js
3902 ms
ScriptResource.axd
2861 ms
ScriptResource.axd
4311 ms
ScriptResource.axd
3145 ms
ScriptResource.axd
2349 ms
CombineScriptsHandler.ashx
5214 ms
0.jpg
5922 ms
XT81599735-6437704.jpg
912 ms
1.jpg
6232 ms
2.jpg
7623 ms
47018684912796.jpg
19913 ms
nablogo.gif
11128 ms
bg.png
1482 ms
ctopsignup.png
1827 ms
ctopsignin.png
2065 ms
searchicon.jpg
1641 ms
backtotop.png
2747 ms
company.aspx
2872 ms
nomap.jpg
2512 ms
live.gif
3384 ms
spec0.jpg
5043 ms
spec1.jpg
14066 ms
spec2.jpg
4778 ms
spec3.jpg
4500 ms
spec4.jpg
10228 ms
loading.gif
6505 ms
more.png
4785 ms
company.aspx
9297 ms
XT81599733-6437703.jpg
912 ms
bgtop.jpg
4916 ms
rmrnutop.png
7266 ms
dark-blue.png
9202 ms
BYekan.woff
15655 ms
menutitlebb.png
7550 ms
contacttop.png
11773 ms
contact.png
9564 ms
contactb.png
8896 ms
bgslidefull.jpg
9115 ms
skitter.styles.css
6922 ms
47018684912796originalcss.css
9055 ms
47018684912796.css
7387 ms
WebResource.axd
7432 ms
WebResource.axd
8213 ms
0.xml
7452 ms
sprite-clean.png
8545 ms
loading.gif
8259 ms
arrows.png
8505 ms
WebResource.axd
9993 ms
notfound.htm
1605 ms
notfound.htm
244 ms
notfound.htm
850 ms
menutitlebb.png
885 ms
notfound.htm
224 ms
0.xml
311 ms
classiccard.oghyanoos.ir SEO score
FA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Classiccard.oghyanoos.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 Classiccard.oghyanoos.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.
classiccard.oghyanoos.ir
Open Graph description is not detected on the main page of Classiccard Oghyanoos. 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: