5.5 sec in total
116 ms
4.1 sec
1.3 sec
Welcome to kateban.com homepage info - get ready to check Kateban best content for Iran right away, or after learning these important things about kateban.com
کاتبان
Visit kateban.comWe analyzed Kateban.com page load time and found that the first response time was 116 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
kateban.com performance score
name
value
score
weighting
Value4.6 s
14/100
10%
Value12.7 s
0/100
25%
Value15.6 s
0/100
10%
Value80 ms
99/100
30%
Value0.373
28/100
15%
Value5.0 s
76/100
10%
116 ms
3016 ms
54 ms
55 ms
72 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 91% of them (61 requests) were addressed to the original Kateban.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Kateban.com.
Page size can be reduced by 279.7 kB (12%)
2.4 MB
2.1 MB
In fact, the total size of Kateban.com main page is 2.4 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.
Potential reduce by 62.1 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 9.4 kB, which is 12% 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 62.1 kB or 80% of the original size.
Potential reduce by 89.0 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. Kateban images are well optimized though.
Potential reduce by 96.8 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 96.8 kB or 64% of the original size.
Potential reduce by 31.8 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. Kateban.com needs all CSS files to be minified and compressed as it can save up to 31.8 kB or 76% of the original size.
Number of requests can be reduced by 18 (30%)
61
43
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kateban. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
kateban.com
116 ms
www.kateban.com
3016 ms
index.css
54 ms
comments.css
55 ms
jquery.min.js
72 ms
index.js
54 ms
comments.js
54 ms
google.js
58 ms
macode.css
79 ms
mainSlider.css
75 ms
jquery.slides.js
78 ms
base.css
27 ms
droidarabicnaskh.css
24 ms
analytics.js
21 ms
font-awesome.min.css
93 ms
menu_sep.png
466 ms
collect
431 ms
back.png
663 ms
DroidNaskh-Bold.woff
429 ms
DroidNaskh-Regular.woff
429 ms
5535280eb1540.jpg
662 ms
55355e39bfc36.png
662 ms
5535598215d76.png
665 ms
55b808ea4f12b.jpg
663 ms
55352a4dd6180.jpg
663 ms
55352b1aefbd7.jpg
664 ms
553551dcb688e.jpg
664 ms
5609946bd789d.jpg
667 ms
55f5d37bbd2f0.png
666 ms
55355839cd19c.png
667 ms
55f2ec85d97cb.jpg
669 ms
5535273ceb26c.png
668 ms
55b7ad7103ab0.jpg
670 ms
55352ac160cdc.jpg
666 ms
55354757801cd.jpg
665 ms
553547d375769.jpg
664 ms
5535485f4c504.jpg
666 ms
55352845f2ea1.jpg
665 ms
5535296838e2d.jpg
665 ms
5535292d969d8.jpg
665 ms
5535490092aa6.jpg
665 ms
55354c9fed5eb.jpg
666 ms
55354ea624eb4.jpg
667 ms
553639a8d6817.jpg
666 ms
kateban_book.png
679 ms
search.png
666 ms
56e55f324a21e.jpg
667 ms
56e339ec6e7b7.jpg
672 ms
56e33513a4989.jpg
667 ms
56e32e9c7f560.jpg
669 ms
56e15de6bb01a.jpg
667 ms
56ded76f0df1d.jpg
674 ms
56d6c273a464d.jpg
672 ms
56cdf978801ae.jpg
672 ms
56cc3800c2f2a.jpg
270 ms
56bf194f2a321.jpg
72 ms
56ab6a2190f23.jpg
77 ms
56dedf3335d18.jpg
49 ms
56a36c6ca1f42.jpg
68 ms
links.png
41 ms
write.png
41 ms
last_comments.png
65 ms
new_comment.png
64 ms
nod_human.png
66 ms
other_centers.png
87 ms
more.png
83 ms
pagination.png
83 ms
kateban.com 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.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
<input type="image"> elements do not have [alt] text
Form elements do not have associated labels
Links do not have a discernible name
kateban.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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
kateban.com 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
FA
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kateban.com 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 Kateban.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.
kateban.com
Open Graph description is not detected on the main page of Kateban. 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: