5.1 sec in total
899 ms
4 sec
221 ms
Click here to check amazing Canary content. Otherwise, check out these important facts you probably never knew about canary.gr
Ελληνικά καναρίνια - Ο Πολυχώρος των φίλων του καναρινιού
Visit canary.grWe analyzed Canary.gr page load time and found that the first response time was 899 ms and then it took 4.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
canary.gr performance score
name
value
score
weighting
Value3.3 s
40/100
10%
Value8.2 s
2/100
25%
Value11.8 s
4/100
10%
Value2,520 ms
4/100
30%
Value0.533
14/100
15%
Value15.3 s
7/100
10%
899 ms
780 ms
146 ms
278 ms
286 ms
Our browser made a total of 99 requests to load all elements on the main page. We found that 55% of them (54 requests) were addressed to the original Canary.gr, 10% (10 requests) were made to Static.xx.fbcdn.net and 8% (8 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Canary.gr.
Page size can be reduced by 145.2 kB (32%)
457.2 kB
312.0 kB
In fact, the total size of Canary.gr main page is 457.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. 45% of websites need less resources to load. Images take 287.2 kB which makes up the majority of the site volume.
Potential reduce by 36.7 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 36.7 kB or 78% of the original size.
Potential reduce by 38.5 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, Canary needs image optimization as it can save up to 38.5 kB or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 52.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 52.5 kB or 52% of the original size.
Potential reduce by 17.5 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. Canary.gr needs all CSS files to be minified and compressed as it can save up to 17.5 kB or 79% of the original size.
Number of requests can be reduced by 53 (56%)
94
41
The browser has sent 94 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Canary. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
canary.gr
899 ms
www.canary.gr
780 ms
x5engine.js
146 ms
styles.css
278 ms
template.css
286 ms
home.css
289 ms
all.js
272 ms
show_ads.js
8 ms
biokipos.gif
227 ms
120X60collagen.gif
890 ms
300x80haritea.gif
593 ms
bg.jpg
841 ms
top.jpg
586 ms
12.gif
315 ms
home_0_04_01.jpg
139 ms
home_0_04_02.jpg
284 ms
home_0_04_03.jpg
286 ms
more.gif
338 ms
home_0_1.jpg
570 ms
home_0_05_01.jpg
413 ms
home_0_05_02.jpg
447 ms
home_0_05_03.jpg
508 ms
home_0_05_04.jpg
568 ms
home_0_05_05.jpg
596 ms
home_0_05_06.jpg
673 ms
home_0_05_07.jpg
689 ms
home_0_05_08.jpg
688 ms
home_0_05_09.jpg
736 ms
home_0_05_010.jpg
736 ms
home_0_05_011.jpg
839 ms
home_0_05_012.jpg
824 ms
home_0_02_01.jpg
825 ms
home_0_02_02.jpg
873 ms
home_0_02_03.jpg
879 ms
home_0_02_04.jpg
960 ms
home_0_02_05.jpg
961 ms
home_0_02_06.jpg
973 ms
home_0_01_01.jpg
1003 ms
home_0_01_02.jpg
1019 ms
home_0_03_01.jpg
1023 ms
home_0_03_02.jpg
1120 ms
home_0_03_03.jpg
1121 ms
content.png
1109 ms
menu.png
1158 ms
immnmn_0.jpg
1151 ms
imcelbghome_0_04.jpg
1157 ms
imcelbghome_0_05.jpg
1209 ms
07.jpg
952 ms
140 ms
zrt_lookup.html
25 ms
show_ads_impl.js
52 ms
xd_arbiter.php
240 ms
xd_arbiter.php
476 ms
imcelbghome_0_02.jpg
1109 ms
ads
252 ms
osd.js
69 ms
ga.js
34 ms
biokipos.gif
346 ms
__utm.gif
36 ms
like_box.php
107 ms
imcelbghome_0_01.jpg
978 ms
imcelbghome_0_03.jpg
1025 ms
bottom.jpg
1154 ms
imsearch.gif
1009 ms
UThj8VI7Xhd.css
336 ms
FL1kvZ1wVUz.css
406 ms
q68gy-v_YMF.js
543 ms
FJmpeSpHpjS.js
673 ms
0wM5s1Khldu.js
538 ms
1bNoFZUdlYZ.js
563 ms
immnmn_1.jpg
968 ms
immnlv_0.jpg
935 ms
css
74 ms
m_js_controller.js
49 ms
abg.js
54 ms
immnlv_1.jpg
896 ms
favicon
47 ms
nessie_icon_tiamat_white.png
30 ms
s
19 ms
googlelogo_color_112x36dp.png
31 ms
x_button_blue2.png
18 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
3 ms
11903905_1072088709471016_634678950216306232_n.jpg
353 ms
11923203_1072088879470999_5387060696526385763_n.jpg
479 ms
10339631_4265549013860_4970882014559175628_n.jpg
607 ms
10959305_632354803532924_1514512339393164405_n.jpg
629 ms
12743533_10205486620834711_842148159620363100_n.jpg
595 ms
12540799_980388925381328_1557982411684420327_n.jpg
555 ms
10933878_10205023762967931_7311359985858598930_n.jpg
688 ms
12507447_990970887626667_2322785930333830084_n.jpg
616 ms
wL6VQj7Ab77.png
71 ms
s7jcwEQH7Sx.png
69 ms
print.css
142 ms
handheld.css
143 ms
accessibility.css
144 ms
I6-MnjEovm5.js
71 ms
pQrUxxo5oQp.js
73 ms
home_0_2.jpg
143 ms
ui
30 ms
canary.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
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
canary.gr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Issues were logged in the Issues panel in Chrome Devtools
canary.gr 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
EL
GR
WINDOWS-1253
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Canary.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 language. Our system also found out that Canary.gr main page’s claimed encoding is windows-1253. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
canary.gr
Open Graph description is not detected on the main page of Canary. 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: