5.3 sec in total
1.5 sec
3.5 sec
371 ms
Visit podi.gr now to see the best up-to-date Podi content for Greece and also check out these interesting facts you probably never knew about podi.gr
Visit podi.grWe analyzed Podi.gr page load time and found that the first response time was 1.5 sec and then it took 3.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
podi.gr performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value11.6 s
0/100
25%
Value12.2 s
3/100
10%
Value1,370 ms
16/100
30%
Value0.192
64/100
15%
Value17.1 s
4/100
10%
1477 ms
286 ms
323 ms
165 ms
402 ms
Our browser made a total of 116 requests to load all elements on the main page. We found that 59% of them (68 requests) were addressed to the original Podi.gr, 18% (21 requests) were made to Maps.google.com and 7% (8 requests) were made to Maps.gstatic.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Podi.gr.
Page size can be reduced by 1.0 MB (40%)
2.6 MB
1.5 MB
In fact, the total size of Podi.gr main page is 2.6 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. 70% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 77.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 77.6 kB or 80% of the original size.
Potential reduce by 118.1 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. Podi images are well optimized though.
Potential reduce by 675.9 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 675.9 kB or 70% of the original size.
Potential reduce by 149.7 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. Podi.gr needs all CSS files to be minified and compressed as it can save up to 149.7 kB or 85% of the original size.
Number of requests can be reduced by 65 (59%)
110
45
The browser has sent 110 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Podi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
www.podi.gr
1477 ms
typography2.php
286 ms
k2.css
323 ms
module_default.css
165 ms
mootools-core.js
402 ms
core.js
164 ms
jquery.min.js
35 ms
k2.js
238 ms
caption.js
244 ms
mootools-more.js
724 ms
acymailing_module.js
318 ms
s5box.js
435 ms
jd.gallery.js
439 ms
jd.gallery.transitions.js
393 ms
css
23 ms
s5_flex_menu.js
476 ms
s5_flex_menu.css
472 ms
system.css
475 ms
general.css
479 ms
template_default.css
517 ms
template.css
552 ms
com_content.css
556 ms
editor.css
555 ms
thirdparty.css
558 ms
s5_responsive_bars.css
534 ms
s5_responsive_hide_classes.css
567 ms
s5_responsive.css
572 ms
custom.css
571 ms
s5_info_slide.css
573 ms
s5_info_slide.js
613 ms
s5_responsive_mobile_bar.js
647 ms
js
27 ms
s5_box_hide_div.js
607 ms
s5_columns_equalizer.js
608 ms
system.css
82 ms
webfont.js
18 ms
analytics.js
17 ms
s5_background.jpg
83 ms
s5_logo.png
84 ms
iacf1.jpg
411 ms
iacf2.jpg
359 ms
iacf3.jpg
259 ms
kotsi.jpg
99 ms
pelmatografima.jpg
257 ms
sport-sience.jpg
257 ms
gonato.jpg
164 ms
diabitiko-podi.jpg
258 ms
pain-management.jpg
408 ms
dna.jpg
408 ms
orthopediki-traumatiologia.jpg
357 ms
ogiatros.jpg
358 ms
va_1.jpg
408 ms
va_2.jpg
409 ms
pelmatography.jpg
409 ms
graph.jpg
480 ms
1386192333_facebook_circle_gray.png
481 ms
1386192351_twitter_circle_gray.png
482 ms
all.js
164 ms
menu_light.png
477 ms
login_light.png
476 ms
register_light.png
479 ms
search_light.png
557 ms
2Q-AW1e_taO6pHwMXcXW5w.ttf
22 ms
collect
25 ms
css
23 ms
s5_header_bg.png
531 ms
facebook.png
532 ms
twitter.png
544 ms
s5_search.png
544 ms
s5_menu_bg.png
545 ms
s5_top_row1.png
577 ms
s5_scroll_arrow.png
538 ms
s5_acc_r_parent.png
491 ms
common.js
9 ms
util.js
20 ms
geocoder.js
19 ms
map.js
17 ms
StaticMapService.GetMapImage
74 ms
AuthenticationService.Authenticate
272 ms
GeocodeService.Search
92 ms
onion.js
16 ms
openhand_8_8.cur
24 ms
ViewportInfoService.GetViewportInfo
59 ms
stats.js
14 ms
controls.js
11 ms
transparent.png
30 ms
css
21 ms
google4.png
33 ms
marker.js
17 ms
mapcnt6.png
20 ms
sv5.png
21 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
35 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
15 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
14 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
15 ms
vt
22 ms
vt
21 ms
tmapctrl.png
23 ms
cb_scout5.png
23 ms
tmapctrl4.png
22 ms
vt
16 ms
loading-bar-black.gif
186 ms
fleche1.png
186 ms
fleche2.png
185 ms
StaticMapService.GetMapImage
91 ms
vt
60 ms
ViewportInfoService.GetViewportInfo
32 ms
tack.png
200 ms
vt
16 ms
vt
18 ms
vt
19 ms
vt
19 ms
vt
19 ms
vt
22 ms
vt
30 ms
infowindow.js
7 ms
podi.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
[aria-hidden="true"] elements contain focusable descendents
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
podi.gr best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
podi.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
EL
EL
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Podi.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 Podi.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.
podi.gr
Open Graph description is not detected on the main page of Podi. 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: