5.2 sec in total
940 ms
3.9 sec
394 ms
Visit g-phone.gr now to see the best up-to-date Gphone content for Greece and also check out these interesting facts you probably never knew about g-phone.gr
Άμεσες επισκευές iphone, ipad και smartphones. Επισκευάζουμε γρήγορα και αποτελεσματικά την χαλασμένη σας συσκευή! Επισκεφθείτε το live repair center της Gphone
Visit g-phone.grWe analyzed G-phone.gr page load time and found that the first response time was 940 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 70% of websites can load faster.
g-phone.gr performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value13.7 s
0/100
25%
Value13.2 s
2/100
10%
Value1,470 ms
14/100
30%
Value0
100/100
15%
Value15.2 s
7/100
10%
940 ms
305 ms
303 ms
766 ms
308 ms
Our browser made a total of 64 requests to load all elements on the main page. We found that 97% of them (62 requests) were addressed to the original G-phone.gr, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain G-phone.gr.
Page size can be reduced by 677.1 kB (24%)
2.8 MB
2.1 MB
In fact, the total size of G-phone.gr main page is 2.8 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. 50% of websites need less resources to load. Images take 2.3 MB which makes up the majority of the site volume.
Potential reduce by 26.2 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 26.2 kB or 79% of the original size.
Potential reduce by 316.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. Obviously, Gphone needs image optimization as it can save up to 316.6 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 257.3 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 257.3 kB or 67% of the original size.
Potential reduce by 77.0 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. G-phone.gr needs all CSS files to be minified and compressed as it can save up to 77.0 kB or 86% of the original size.
Number of requests can be reduced by 12 (19%)
63
51
The browser has sent 63 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Gphone. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 8 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
g-phone.gr
940 ms
jcemediabox.css
305 ms
style.css
303 ms
mootools.js
766 ms
caption.js
308 ms
jcemediabox.js
613 ms
jquery-1.7.2.min.js
789 ms
system.css
452 ms
general.css
457 ms
template.css
917 ms
custom.css
603 ms
jquery.js
931 ms
script.js
1050 ms
slideshow.js
787 ms
ga.js
112 ms
pageglare.png
160 ms
header.jpg
154 ms
logo_2.png
154 ms
eikona.png
158 ms
call-mail2.png
307 ms
object839133784.png
307 ms
nav.png
301 ms
menuactiveitem.png
306 ms
arxikh_ic.png
309 ms
spacer.gif
309 ms
a.jpg
902 ms
b.jpg
768 ms
c.jpg
1072 ms
d.jpg
767 ms
e.jpg
927 ms
f.jpg
925 ms
g.jpg
925 ms
iphone.png
924 ms
ipad.png
1052 ms
ipod.png
1122 ms
nokia.png
1120 ms
samsung.png
1121 ms
sony.png
1120 ms
lg.png
1206 ms
blackberry.png
1225 ms
4.png
1273 ms
1.jpg
1275 ms
2.jpg
1273 ms
3.png
1274 ms
surprised.png
1356 ms
acsSend.png
1377 ms
service1.jpg
1579 ms
Service2.jpg
1578 ms
Service3.png
1580 ms
facebook_icon.png
1428 ms
popup.html
1443 ms
__utm.gif
12 ms
tooltip.html
1386 ms
tweet_icon.png
1436 ms
google_icon.png
1510 ms
youtube_icon.png
1531 ms
pr_icon.png
1439 ms
agorainfo.png
1434 ms
loader.gif
1439 ms
postbullets.png
1439 ms
footer.png
1509 ms
footer_bg.png
1686 ms
captionbg.png
1123 ms
go_style3.png
1124 ms
g-phone.gr 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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Links do not have a discernible name
g-phone.gr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
g-phone.gr SEO score
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 G-phone.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 G-phone.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.
g-phone.gr
Open Graph description is not detected on the main page of Gphone. 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: