4.9 sec in total
564 ms
3.8 sec
505 ms
Visit gpce.gr now to see the best up-to-date Gpce content and also check out these interesting facts you probably never knew about gpce.gr
G.P.C.E. started as a third party operative on a national level, but it is now well established on a more international field, undertalking projects of any scale, due to the large number of assets tha...
Visit gpce.grWe analyzed Gpce.gr page load time and found that the first response time was 564 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
gpce.gr performance score
564 ms
145 ms
143 ms
171 ms
168 ms
Our browser made a total of 86 requests to load all elements on the main page. We found that 77% of them (66 requests) were addressed to the original Gpce.gr, 9% (8 requests) were made to Apis.google.com and 2% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Gpce.gr.
Page size can be reduced by 221.6 kB (9%)
2.4 MB
2.2 MB
In fact, the total size of Gpce.gr 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. 45% of websites need less resources to load. Images take 2.2 MB which makes up the majority of the site volume.
Potential reduce by 19.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. 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 19.6 kB or 72% of the original size.
Potential reduce by 94.6 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. Gpce images are well optimized though.
Potential reduce by 93.7 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 93.7 kB or 66% of the original size.
Potential reduce by 13.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. Gpce.gr needs all CSS files to be minified and compressed as it can save up to 13.8 kB or 72% of the original size.
Number of requests can be reduced by 25 (30%)
83
58
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gpce. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 20 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
gpce.gr
564 ms
reset.css
145 ms
skeleton.css
143 ms
superfish.css
171 ms
style.css
168 ms
slider.css
167 ms
touchTouch.css
171 ms
css
25 ms
jquery-1.7.1.min.js
357 ms
script.js
304 ms
jquery.hoverIntent.js
302 ms
superfish.js
331 ms
jquery.responsivemenu.js
334 ms
jquery.ui.totop.js
337 ms
jquery.easing.1.3.js
433 ms
jquery.kwicks-1.5.1.js
465 ms
jquery.flexslider-min.js
469 ms
touchTouch.jquery.js
492 ms
body-tail.gif
80 ms
slide1-color.jpg
412 ms
slide1.jpg
549 ms
slide2-color.jpg
423 ms
slide2.jpg
805 ms
slide3-color.jpg
511 ms
slide3.jpg
654 ms
slide4-color.jpg
988 ms
slide4.jpg
1077 ms
page1-icon1.png
701 ms
page1-icon2.png
738 ms
page1-icon3.png
818 ms
page1-icon4.png
871 ms
page1-img1.jpg
994 ms
page1-img2.jpg
1146 ms
page1-img3.jpg
1161 ms
page1-img4.jpg
1143 ms
shipyard_1.jpg
1179 ms
shipyard_2.jpg
1186 ms
shipyard_3.jpg
1318 ms
shipyard_4.jpg
1384 ms
shipyard_5.jpg
1351 ms
shipyard_6.jpg
1401 ms
all.js
282 ms
header-tail.gif
1315 ms
header-gradient.gif
1419 ms
slider-tail.gif
1441 ms
logo.png
1444 ms
menu-tail.gif
1507 ms
menu-separator.gif
1505 ms
menu-hover.gif
1523 ms
submenu-tail.gif
1583 ms
caption-tail.png
1568 ms
caption-link.png
1606 ms
content-tail.gif
1634 ms
box-tail.gif
1634 ms
box-gradient.jpg
1684 ms
plusone.js
65 ms
Y_TKV6o8WovbUd3m_X9aAA.ttf
13 ms
box-separator.png
1640 ms
cb=gapi.loaded_0
10 ms
cb=gapi.loaded_1
6 ms
fastbutton
67 ms
postmessageRelay
65 ms
cb=gapi.loaded_0
27 ms
cb=gapi.loaded_1
35 ms
W5F8_SL0XFawnjxHGsZjJA.ttf
29 ms
3193398744-postmessagerelay.js
28 ms
rpc:shindig_random.js
31 ms
cb=gapi.loaded_0
3 ms
127 ms
xd_arbiter.php
209 ms
xd_arbiter.php
418 ms
button-tail.gif
1318 ms
link-marker.gif
1361 ms
pic1.gif
1303 ms
marker-1.gif
1265 ms
button-tail1.gif
1212 ms
aside-tail.gif
1178 ms
magnifier.png
1153 ms
footer-tail.gif
1144 ms
icon-1.png
1157 ms
icon-5.png
1104 ms
menu-arrow.gif
1022 ms
totop.png
84 ms
like.php
84 ms
TY3MhkXpWJ-.js
484 ms
LVx-xkvaJ0b.png
544 ms
gpce.gr SEO score
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gpce.gr can be misinterpreted by Google and other search engines. Our service has detected that English 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 Gpce.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.
gpce.gr
Open Graph description is not detected on the main page of Gpce. 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: