6 sec in total
1.2 sec
3.9 sec
930 ms
Visit noesi.gr now to see the best up-to-date Noesi content for Greece and also check out these interesting facts you probably never knew about noesi.gr
Visit noesi.grWe analyzed Noesi.gr page load time and found that the first response time was 1.2 sec and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
noesi.gr performance score
name
value
score
weighting
Value3.5 s
35/100
10%
Value5.0 s
27/100
25%
Value5.6 s
53/100
10%
Value620 ms
48/100
30%
Value0.088
92/100
15%
Value10.2 s
25/100
10%
1175 ms
187 ms
189 ms
190 ms
286 ms
Our browser made a total of 165 requests to load all elements on the main page. We found that 28% of them (47 requests) were addressed to the original Noesi.gr, 25% (41 requests) were made to Maps.googleapis.com and 12% (19 requests) were made to Mt.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Noesi.gr.
Page size can be reduced by 2.6 MB (52%)
4.9 MB
2.3 MB
In fact, the total size of Noesi.gr main page is 4.9 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 2.9 MB which makes up the majority of the site volume.
Potential reduce by 84.3 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 84.3 kB or 80% of the original size.
Potential reduce by 116.4 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. Noesi images are well optimized though.
Potential reduce by 1.9 MB
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 1.9 MB or 67% of the original size.
Potential reduce by 461.4 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. Noesi.gr needs all CSS files to be minified and compressed as it can save up to 461.4 kB or 86% of the original size.
Number of requests can be reduced by 89 (56%)
159
70
The browser has sent 159 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Noesi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 48 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.
www.noesi.gr
1175 ms
css_pbm0lsQQJ7A7WCCIMgxLho6mI_kBNgznNUWmTWcnfoE.css
187 ms
css_YbFUeFzwaYf35_AWwZDLccOPP6KjlVFJ2H27uDhg3Jw.css
189 ms
css_nuG_KvIRECfRfpWIvmLEfrOS8pR4HZ6SeR75uTmLnac.css
190 ms
css_Y9PbVgYvMP_vRNYi5oHVcqBZO-OptzDj7rEiIKUflSc.css
286 ms
css_amTWFGZogFVAVpGrw9wWCxJNZHMGUlwICehqLCUnvnk.css
189 ms
css_-uaz_zEbJr6Uw9ReBd0ZHWabxU746CFUTsndzFtZCaQ.css
190 ms
css_02EQLUpe3OSFKJU45UUv7CcyczorGwyohKK3DiAh72U.css
278 ms
css_s0yuw0hVULEaJarvbuSCglopkTbBrpI2G58uGNl-AN4.css
281 ms
js_xAPl0qIk9eowy_iS9tNkCWXLUVoat94SQT48UBCFkyQ.js
374 ms
js_n7Lw7PPN-xdTJcPryjHWWwcX-NVLfdUvNwg6eFAlc8I.js
282 ms
js_w6HPyPSB4upLY6ME3kFuM5AyvchuX0d21TJNXBJ7ZKM.js
302 ms
js_ZS_Fu9Rt9DYTjU6nZF6ooeRyPlAhgmo3biUxOX3rBF8.js
385 ms
js_lixepc3_Jq37wMPlwValwq99J8iaJPNIvPuUJ7rMTZ4.js
387 ms
ExoqIgs3qVo
293 ms
ms
210 ms
embed
582 ms
btn_donate_LG.gif
159 ms
pixel.gif
160 ms
logo.png
365 ms
main-nav-hover.png
152 ms
icon-home.png
150 ms
icon-blog.png
151 ms
icon-books.png
151 ms
icon-groups.png
150 ms
icon-events.png
239 ms
ico_search_wht.png
235 ms
commons-drop.png
342 ms
noesigr-build-facebook-banner-01.gif
238 ms
noesigr-build-facebook-banner-04.gif
242 ms
noesigr-build-facebook-banner-03.gif
342 ms
noesigr-build-facebook-banner-02.gif
342 ms
noesigr-build-facebook-banner-05.gif
337 ms
icons-s0eb3728c55.png
338 ms
icon-more.png
421 ms
unnamed.jpg
1778 ms
picture-default.jpg
417 ms
picture-23083-1451315587.jpg
421 ms
book-of-news.JPG
543 ms
book-of-noesi.JPG
542 ms
book-of-syndromes.JPG
635 ms
book-of-services.JPG
635 ms
book-of-syndromes2.JPG
769 ms
user_img_arrow.png
634 ms
picture-2-1367964701.png
633 ms
picture-default.jpg
854 ms
node-promoted-star.png
855 ms
picture-3181-1450015970.jpg
854 ms
picture-23083-1451315587.jpg
854 ms
HONConduct496759_s.gif
864 ms
dc.js
88 ms
likebox.php
137 ms
__utm.gif
13 ms
embed
663 ms
illust_1200x1000-02_900x750.jpg
755 ms
www-embed-player-vflZsBgOl.css
84 ms
www-embed-player.js
106 ms
base.js
183 ms
roNeOY-tz5Y.css
260 ms
UHhaxo8Cs3k.css
261 ms
_rx8naC75Dy.js
341 ms
x5F9OMjKyLw.js
408 ms
ICDbTSzjQEg.js
355 ms
TTCre3391I0.js
339 ms
6BOEML_YqI6cKINK5dmh8ZufcXg7sBa4jeB-I9gQ0xI.js
50 ms
ad_status.js
116 ms
QHD8zigcbDB8aPfIoaupKOvvDin1pK8aKteLpeZ5c0A.ttf
107 ms
RxZJdnzeo3R5zSexge8UUSZ2oysoEQEeKwjgmXLRnTc.ttf
115 ms
rs=ABjfnFUHhxYFyvqPfpD3q5iglaMJ5n0z5g
120 ms
css
135 ms
js
207 ms
rs=ABjfnFWzP5qdMsbAb94_TbBMIAezV3tysg
223 ms
11013512_10153123264159161_5887660569531999474_n.jpg
459 ms
11037222_10153211385374161_6446552311842825186_n.jpg
516 ms
199673_1010929412726_159619_n.jpg
670 ms
10426156_854966721216136_7095331695639477281_n.jpg
704 ms
12187746_182065715466941_5293168034154777207_n.jpg
699 ms
12243376_1665459937071615_6866317604801838999_n.jpg
669 ms
528606_104295963041211_701409885_n.jpg
669 ms
wL6VQj7Ab77.png
147 ms
s7jcwEQH7Sx.png
146 ms
rs=ABjfnFWzP5qdMsbAb94_TbBMIAezV3tysg
46 ms
common.js
52 ms
map.js
87 ms
overlay.js
140 ms
1201-fac-info-alt.png&filter=ff&scale=1.0
260 ms
util.js
155 ms
marker.js
139 ms
geocoder.js
129 ms
controls.js
146 ms
places_impl.js
128 ms
selection_2x-000.png
53 ms
22-blue-dot.png&filter=ff&scale=1.0
322 ms
157-yellow-dot.png&filter=ff&scale=1.0
373 ms
62-green.png&filter=ff&scale=1.0
376 ms
61-green-dot.png&filter=ff&scale=1.0
402 ms
1493-wht-blank_maps-4x.png&filter=ffF4B400&scale=1.0
406 ms
158-yellow.png&filter=ff&scale=1.0
403 ms
24-blue.png&filter=ff&scale=1.0
407 ms
js
141 ms
rs=ABjfnFXiT3Z7ViGxfD9m1-BFQB2jVKEBSw
121 ms
d-6IYplOFocCacKzxwXSOCZ2oysoEQEeKwjgmXLRnTc.ttf
113 ms
Hgo13k-tfSpn0qi1SFdUfSZ2oysoEQEeKwjgmXLRnTc.ttf
135 ms
gen204
108 ms
onion.js
215 ms
openhand_8_8.cur
395 ms
ViewportInfoService.GetViewportInfo
244 ms
stats.js
186 ms
StaticMapService.GetMapImage
232 ms
rs=ABjfnFXiT3Z7ViGxfD9m1-BFQB2jVKEBSw
191 ms
common.js
215 ms
map.js
202 ms
overlay.js
202 ms
util.js
209 ms
marker.js
195 ms
geocoder.js
186 ms
controls.js
282 ms
places_impl.js
283 ms
168-ylw-pushpin.png&filter=ff&scale=1.0
153 ms
169-ltblue-dot.png&filter=ff&scale=1.0
184 ms
gen204
157 ms
transparent.png
238 ms
mapcnt6.png
178 ms
tmapctrl4.png
199 ms
vt
105 ms
vt
104 ms
vt
102 ms
vt
132 ms
vt
133 ms
vt
156 ms
vt
133 ms
onion.js
79 ms
ViewportInfoService.GetViewportInfo
76 ms
stats.js
56 ms
I6-MnjEovm5.js
140 ms
vlXaquuXMrr.js
141 ms
viewer-icons001.png
93 ms
star4.png
107 ms
1201-fac-info-alt.png&scale=1.0
74 ms
gen204
104 ms
AuthenticationService.Authenticate
52 ms
MyMaps_Icons003.png
41 ms
mymaps_32.png
46 ms
v1_4593b7d7.png
51 ms
google-my-maps-logo-small-001.png
51 ms
22-blue-dot.png&scale=1.0
39 ms
157-yellow-dot.png&scale=1.0
40 ms
62-green.png&scale=1.0
41 ms
61-green-dot.png&scale=1.0
42 ms
158-yellow.png&scale=1.0
49 ms
24-blue.png&scale=1.0
43 ms
vt
69 ms
kh
79 ms
vt
61 ms
vt
59 ms
vt
56 ms
vt
52 ms
vt
76 ms
vt
99 ms
168-ylw-pushpin.png&scale=1.0
89 ms
AuthenticationService.Authenticate
46 ms
169-ltblue-dot.png&scale=1.0
47 ms
kh
44 ms
css_6b38QoA10iNo0WlQABsPuoYUzGFZrPw1WER3vGjCXdw.css
87 ms
transparent.png
13 ms
noesi.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 IDs are not unique
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
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
noesi.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
noesi.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 Noesi.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 Noesi.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.
noesi.gr
Open Graph description is not detected on the main page of Noesi. 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: