7.3 sec in total
1.2 sec
5.7 sec
383 ms
Welcome to hcg.gr homepage info - get ready to check Hcg best content for Greece right away, or after learning these important things about hcg.gr
Καλώς ήρθατε στον ιστότοπο του ΛΣ-ΕΛΑΚΤ
Visit hcg.grWe analyzed Hcg.gr page load time and found that the first response time was 1.2 sec and then it took 6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
hcg.gr performance score
name
value
score
weighting
Value6.9 s
1/100
10%
Value15.2 s
0/100
25%
Value17.5 s
0/100
10%
Value0 ms
100/100
30%
Value0.844
4/100
15%
Value6.9 s
53/100
10%
1238 ms
255 ms
255 ms
256 ms
272 ms
Our browser made a total of 121 requests to load all elements on the main page. We found that 77% of them (93 requests) were addressed to the original Hcg.gr, 10% (12 requests) were made to Eweather.gr and 5% (6 requests) were made to Trustlogo.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Hcg.gr.
Page size can be reduced by 720.0 kB (54%)
1.3 MB
614.5 kB
In fact, the total size of Hcg.gr main page is 1.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. 40% of websites need less resources to load. Javascripts take 515.4 kB which makes up the majority of the site volume.
Potential reduce by 51.6 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.1 kB, which is 14% 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 51.6 kB or 81% of the original size.
Potential reduce by 37.8 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. Hcg images are well optimized though.
Potential reduce by 357.4 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 357.4 kB or 69% of the original size.
Potential reduce by 273.2 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. Hcg.gr needs all CSS files to be minified and compressed as it can save up to 273.2 kB or 82% of the original size.
Number of requests can be reduced by 53 (46%)
114
61
The browser has sent 114 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Hcg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 21 to 1 for JavaScripts and from 29 to 1 for CSS and as a result speed up the page load time.
hcg.gr
1238 ms
system.base.css
255 ms
system.menus.css
255 ms
system.messages.css
256 ms
system.theme.css
272 ms
shadowbox.css
275 ms
aggregator.css
505 ms
book.css
505 ms
comment.css
528 ms
field.css
544 ms
node.css
543 ms
search.css
757 ms
user.css
773 ms
forum.css
804 ms
views.css
812 ms
ctools.css
688 ms
datepicker.1.7.css
803 ms
ldap_help.css
905 ms
panels.css
916 ms
views_slideshow.css
928 ms
extlink.css
942 ms
views-slideshow-ddblock-cycle-vsddefault.css
943 ms
date.css
1056 ms
layout.css
1179 ms
style.css
1550 ms
colors.css
1178 ms
boxes.css
1196 ms
corners_97cbee.css
1210 ms
print.css
1312 ms
jquery.js
2005 ms
jquery.once.js
1453 ms
drupal.js
1608 ms
shadowbox.js
2035 ms
el_d9x-4ObYsSIqgIiukmuma7RNmULgscIKtnXygPzV6yg.js
1696 ms
panels.js
1729 ms
shadowbox_auto.js
1818 ms
views_slideshow.js
1906 ms
formoptions.js
1837 ms
extlink.js
1882 ms
jquery.cycle.all.min.js
1936 ms
json2.pack.js
2071 ms
views_slideshow_ddblock.js
2046 ms
googleanalytics.js
1911 ms
jquery.ui.dialog.patch.js
1900 ms
analytics.js
19 ms
trustlogo.js
39 ms
collect
28 ms
trustlogo.js
57 ms
extlink.png
132 ms
121 ms
fbook-40x40.jpg
513 ms
xamogelo.png
505 ms
europa-flag.jpg
540 ms
sailGreece.png
818 ms
ombudsmangrsm.png
542 ms
ombudsmansm.png
545 ms
banner300311.jpg
412 ms
ethnosimo.png
511 ms
transparent_bg.png
341 ms
ERT_MARK_0.jpg
519 ms
MARK_15_1.jpg
558 ms
OHE%20m.jpg
659 ms
SND%20m.jpg
817 ms
prev.png
664 ms
next.png
771 ms
ERT_MARK_0.jpg
781 ms
MARK_15_1.jpg
835 ms
OHE%20m.jpg
935 ms
SND%20m.jpg
939 ms
box420x32.png
1040 ms
myt%20m.jpg
1057 ms
204sm.jpg
1087 ms
IMG_0525m.jpg
1102 ms
20160224m.jpg
1191 ms
narkwt_kavala_mark.jpg
1214 ms
Social_RSS.png
1310 ms
Social_Email_RSS.png
1331 ms
Social_Twitter.png
1336 ms
Social_Youtube.png
1371 ms
ecgff.jpg
1459 ms
emsa2015.jpg
1464 ms
imgEvepe.jpg
1585 ms
xartaboat.jpg
1591 ms
box275x30.png
1592 ms
search-button.png
1640 ms
icon_e.png
1715 ms
kad_240x60.jpg
1721 ms
IMO.jpg
1861 ms
emsa.jpg
1863 ms
frontex.jpg
1865 ms
ecgff.jpg
1916 ms
hbox.php
1541 ms
seal_bg.gif
36 ms
seal_bg.gif
8 ms
warranty_level.gif
10 ms
comodo_secure_76x26_transp.png
706 ms
warranty_level.gif
7 ms
www-embed-player-vflZsBgOl.css
64 ms
www-embed-player.js
84 ms
base.js
147 ms
ssn.jpg
1870 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
34 ms
ad_status.js
33 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
78 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
87 ms
newmlc.jpg
1659 ms
stcw3.jpg
1716 ms
hmco.jpg
1903 ms
diavgeia.jpg
1623 ms
map_Greeece.png
1870 ms
h4.png
185 ms
T23000.png
186 ms
02135.png
191 ms
T13000.png
187 ms
04315.png
194 ms
T12000.png
195 ms
04225.png
366 ms
05225.png
374 ms
04180.png
371 ms
magnifying-glass.gif
372 ms
logo.png
375 ms
hcg.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
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[role]s are not contained by their required parent element
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
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
hcg.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
Displays images with incorrect aspect ratio
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
hcg.gr SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
robots.txt is not valid
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
EL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hcg.gr can be misinterpreted by Google and other search engines. Our service has detected that Greek is used on the page, and it matches the claimed language. Our system also found out that Hcg.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.
hcg.gr
Open Graph description is not detected on the main page of Hcg. 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: