1.8 sec in total
12 ms
1.5 sec
251 ms
Visit kodoom.com now to see the best up-to-date Kodoom content for United States and also check out these interesting facts you probably never knew about kodoom.com
آخرین اخبار مربوط به ایران و رویدادهای ایرانی را در کدوم بخوانید.
Visit kodoom.comWe analyzed Kodoom.com page load time and found that the first response time was 12 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
kodoom.com performance score
name
value
score
weighting
Value11.7 s
0/100
10%
Value14.8 s
0/100
25%
Value12.0 s
4/100
10%
Value280 ms
81/100
30%
Value0.111
87/100
15%
Value16.5 s
5/100
10%
12 ms
99 ms
32 ms
56 ms
7 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 28% of them (26 requests) were addressed to the original Kodoom.com, 26% (24 requests) were made to I.kdcdn.com and 17% (16 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (537 ms) relates to the external source Staticxx.facebook.com.
Page size can be reduced by 3.4 MB (65%)
5.3 MB
1.8 MB
In fact, the total size of Kodoom.com main page is 5.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 3.5 MB which makes up the majority of the site volume.
Potential reduce by 189.0 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 36.5 kB, which is 16% 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 189.0 kB or 84% of the original size.
Potential reduce by 18.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. Kodoom images are well optimized though.
Potential reduce by 862.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 862.9 kB or 67% of the original size.
Potential reduce by 2.4 MB
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. Kodoom.com needs all CSS files to be minified and compressed as it can save up to 2.4 MB or 68% of the original size.
Number of requests can be reduced by 62 (72%)
86
24
The browser has sent 86 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kodoom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 27 to 1 for CSS and as a result speed up the page load time.
kodoom.com
12 ms
www.kodoom.com
99 ms
desktop-style.min.css
32 ms
main.min.js
56 ms
jquery.nicescroll.min.js
7 ms
big-slider.js
6 ms
js
103 ms
iframe_api
49 ms
kodoom-logo-since-2008.png
216 ms
search-arrow-down.gif
216 ms
aOvfti4-600-372.jpg
211 ms
common.js
198 ms
map.js
217 ms
util.js
277 ms
marker.js
265 ms
all.js
529 ms
NK4MAJM-600-372.jpg
119 ms
k25rEEW-600-372.jpg
119 ms
vc9f2RV-600-372.jpg
147 ms
9yQDgNR-600-372.jpg
141 ms
hV8tcsm-600-372.jpg
144 ms
mgoc3.jpg
93 ms
dvvyaiS-600-372.jpg
145 ms
p8xuk.jpg
268 ms
1nise.jpg
147 ms
4nliwDT-300-ns.jpg
150 ms
i4irHeE-300-ns.jpg
151 ms
ZphvhT1-100-62.jpg
147 ms
nltgYre-100-62.jpg
148 ms
9xCnlWA-100-62.jpg
147 ms
WykpLDo-100-62.jpg
150 ms
JmKyIYd-100-62.jpg
269 ms
sxrvjaY-100-62.jpg
150 ms
ixVJaPJ-100-62.jpg
264 ms
qPSC3zx-100-62.jpg
265 ms
N7JdEXA-100-62.jpg
265 ms
qkhzr1H-100-62.jpg
151 ms
i9Hx9sI-100-62.jpg
152 ms
1hk50Pm-100-62.jpg
410 ms
nav-arrow-down.png
87 ms
ticket.png
87 ms
right-arrow.png
89 ms
left-arrow.png
90 ms
event.png
90 ms
sale.png
89 ms
up.png
115 ms
down.png
115 ms
bullet_yellow2.png
138 ms
kodoom_sprite.png
139 ms
toggle-32.png
139 ms
skip-32.png
139 ms
mute-32.png
141 ms
bg_kodoom.png
143 ms
nassim-bold.woff
145 ms
nassim.woff
145 ms
StaticMapService.GetMapImage
264 ms
www-widgetapi.js
90 ms
widgets.js
212 ms
ga.js
39 ms
imp
93 ms
yql
461 ms
__utm.gif
152 ms
overlay.png
152 ms
bx_loader.gif
153 ms
onion.js
140 ms
ViewportInfoService.GetViewportInfo
256 ms
stats.js
114 ms
controls.js
111 ms
transparent.png
261 ms
css
230 ms
161 ms
google4.png
165 ms
mapcnt6.png
172 ms
sv5.png
194 ms
vt
130 ms
vt
127 ms
vt
110 ms
vt
110 ms
vt
111 ms
spotlight-poi.png
90 ms
183 ms
www-embed-player-vflZsBgOl.css
193 ms
www-embed-player.js
220 ms
xd_arbiter.php
338 ms
xd_arbiter.php
537 ms
AuthenticationService.Authenticate
45 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
41 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
40 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
47 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
69 ms
yrK4EqpSRdoujKQmsJoZ5WaLgeULvcWnibQMQSxOOnM.js
103 ms
ad_status.js
101 ms
xd_arbiter.php
137 ms
kodoom.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
ARIA IDs are not unique
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.
kodoom.com 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
Browser errors were logged to the console
Page has valid source maps
kodoom.com 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 Kodoom.com 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 Kodoom.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.
kodoom.com
Open Graph description is not detected on the main page of Kodoom. 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: