6.5 sec in total
1.7 sec
4.6 sec
256 ms
Visit kati.gr now to see the best up-to-date Kati content for Greece and also check out these interesting facts you probably never knew about kati.gr
Visit kati.grWe analyzed Kati.gr page load time and found that the first response time was 1.7 sec and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
kati.gr performance score
name
value
score
weighting
Value4.6 s
13/100
10%
Value8.9 s
1/100
25%
Value10.2 s
9/100
10%
Value3,150 ms
2/100
30%
Value0.251
49/100
15%
Value13.2 s
12/100
10%
1655 ms
1454 ms
1188 ms
1190 ms
1190 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 85% of them (60 requests) were addressed to the original Kati.gr, 4% (3 requests) were made to Facebook.com and 4% (3 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.9 sec) belongs to the original domain Kati.gr.
Page size can be reduced by 176.9 kB (49%)
361.2 kB
184.3 kB
In fact, the total size of Kati.gr main page is 361.2 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. 25% of websites need less resources to load. Images take 172.9 kB which makes up the majority of the site volume.
Potential reduce by 55.9 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 55.9 kB or 78% of the original size.
Potential reduce by 48.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. Obviously, Kati needs image optimization as it can save up to 48.0 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 53.5 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 53.5 kB or 58% of the original size.
Potential reduce by 19.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. Kati.gr needs all CSS files to be minified and compressed as it can save up to 19.4 kB or 79% of the original size.
Number of requests can be reduced by 40 (57%)
70
30
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Kati. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
kati.gr
1655 ms
style.css
1454 ms
rating.css
1188 ms
thumbs.css
1190 ms
resize.css
1190 ms
minmax.css
1192 ms
datepicker.css
1191 ms
jquery-1.2.3.min.js
1874 ms
cookie.js
1327 ms
rating.js
1462 ms
sessvars.js
1465 ms
esyndicat.js
1328 ms
category-tree-style.css
1485 ms
FB.Share
15 ms
banners.js
1041 ms
thumbs.js
1079 ms
utils.js
1079 ms
minmax.js
1078 ms
esyndicat.search.js
1077 ms
body-top-bg.gif
436 ms
logo.png
434 ms
text-bg.gif
436 ms
facebook_16.png
434 ms
twitter_16.png
435 ms
google_16.png
433 ms
diggit_16.png
569 ms
stumbleupon_16.png
573 ms
linkedin_16.png
573 ms
yahoo_16.png
574 ms
54.jpg
843 ms
35.gif
700 ms
73.jpg
706 ms
67.jpg
711 ms
72.png
1392 ms
75.png
1025 ms
6.gif
977 ms
5.gif
843 ms
68.gif
847 ms
9.jpg
980 ms
2.gif
980 ms
1.gif
985 ms
7.gif
1103 ms
34.gif
1116 ms
25.gif
1120 ms
4.jpg
1123 ms
ajax-loader.gif
1161 ms
spinner.gif
1238 ms
tab-left-act.gif
1211 ms
tab-right-act.gif
1213 ms
tab-left.gif
1219 ms
tab-right.gif
1257 ms
movable-box-caption-orange.gif
1331 ms
movable-box-caption-left.gif
1348 ms
movable-box-caption-right.gif
1350 ms
box-content-top.gif
1357 ms
like.php
431 ms
353 ms
xd_arbiter.php
458 ms
xd_arbiter.php
573 ms
ga.js
43 ms
share_button.php
107 ms
ico-dir.gif
1010 ms
movable-box-caption-blue.gif
1078 ms
movable-box-caption-purple.gif
1097 ms
body-bot-bg.gif
1097 ms
thumb-bg.gif
1176 ms
minmax.gif
1106 ms
__utm.gif
61 ms
fy8tT2klpgR.js
277 ms
LVx-xkvaJ0b.png
307 ms
fy8tT2klpgR.js
412 ms
kati.gr 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-*] attributes do not match their roles
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements 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
<frame> or <iframe> elements do not have a title
Form elements do not have associated labels
Links do not have a discernible name
kati.gr 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
kati.gr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
EL
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Kati.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it does not match the claimed English language. Our system also found out that Kati.gr 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.
kati.gr
Open Graph description is not detected on the main page of Kati. 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: