3.8 sec in total
353 ms
2.8 sec
700 ms
Click here to check amazing Fpress content for Greece. Otherwise, check out these important facts you probably never knew about fpress.gr
Τα σημαντικότερα οικονομικά, επιχειρηματικά και τραπεζικά νέα με την υπογραφή του Νίκου Σαμοΐλη.
Visit fpress.grWe analyzed Fpress.gr page load time and found that the first response time was 353 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
fpress.gr performance score
name
value
score
weighting
Value3.1 s
46/100
10%
Value8.9 s
1/100
25%
Value4.7 s
69/100
10%
Value740 ms
40/100
30%
Value0.258
48/100
15%
Value10.0 s
27/100
10%
353 ms
337 ms
242 ms
164 ms
248 ms
Our browser made a total of 93 requests to load all elements on the main page. We found that 84% of them (78 requests) were addressed to the original Fpress.gr, 3% (3 requests) were made to Secure-uk.imrworldwide.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (968 ms) belongs to the original domain Fpress.gr.
Page size can be reduced by 717.1 kB (31%)
2.3 MB
1.6 MB
In fact, the total size of Fpress.gr main page is 2.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. 65% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 81.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 14.6 kB, which is 15% 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 81.6 kB or 82% of the original size.
Potential reduce by 86.9 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. Fpress images are well optimized though.
Potential reduce by 464.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 464.9 kB or 66% of the original size.
Potential reduce by 83.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. Fpress.gr needs all CSS files to be minified and compressed as it can save up to 83.7 kB or 84% of the original size.
Number of requests can be reduced by 37 (41%)
91
54
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Fpress. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
fpress.gr
353 ms
www.fpress.gr
337 ms
theme_v8.css
242 ms
modal.css
164 ms
k2.css
248 ms
keeGrid_v2.css
167 ms
slideshow.css
168 ms
tools.css
181 ms
style-7-websites.css
242 ms
style.portal.mode.3.css
248 ms
style.portal.mode.2.css
246 ms
template.css.php
267 ms
mootools-core.js
483 ms
core.js
320 ms
modal.js
324 ms
jquery-1.8.2.min.js
574 ms
k2.noconflict.js
328 ms
k2.js
355 ms
jsapi
17 ms
script-7-websites.js
399 ms
template.js
404 ms
menu.js
408 ms
jquery.tools.min.js
622 ms
mootools-more.js
968 ms
engine.portal.mode.3.js
508 ms
engine.portal.mode.2.js
509 ms
jquery.min.js
52 ms
jquery.fpss.js
560 ms
v60.js
47 ms
gpt.js
15 ms
ga.js
46 ms
headers.jpg
172 ms
logo-typo.png
110 ms
m-right.png
111 ms
icon-search.jpg
111 ms
loading.gif
101 ms
1738_f1c4dafe9b2166c170d3410acf419ec3_m.jpg
175 ms
transparent_bg.png
157 ms
1738_f1c4dafe9b2166c170d3410acf419ec3_t.jpg
159 ms
karfota.jpg
324 ms
label.png
181 ms
c55568ecf026652052636d6774b452cb_S.jpg
235 ms
12c7512de08712c5046d40d2f955deb5_S.jpg
236 ms
806cf02471683a9ad4274377d772861f_S.jpg
320 ms
66d01b03e380897264b9737601bd1a4d_S.jpg
258 ms
f04c6ec7cff7942c8fc2acdf978cabf6_S.jpg
360 ms
nsp_portal_mode_3_interface.png
316 ms
k2.items.cache.62f4ae92849d28369f0c1b400f2a3bf4_Lnsp_356.jpg
404 ms
item-read-more.png
340 ms
k2.items.cache.761e66c60b82c5459ca9ca7f18aca011_Lnsp_356.jpg
397 ms
k2.items.cache.006c5775f46ab22d2af96ac74c980410_Lnsp_356.jpg
485 ms
k2.items.cache.e44f6ae1e2f2af9af253ae52b94b2b68_Lnsp_356.jpg
573 ms
k2.items.cache.4651481c36291d16c99a59bd3752ff1b_Lnsp_356.jpg
505 ms
k2.items.cache.5136aa7d6c146dbc06fe1d9b9ce953c5_Lnsp_356.jpg
629 ms
k2.items.cache.ac7be24885781cd0e589357b2c026b18_Lnsp_356.jpg
479 ms
k2.items.cache.42af4abbc5d4c1954d1d80a2d58103c4_Lnsp_356.jpg
569 ms
k2.items.cache.65051f11f7e5efd0b9b78a252bca070a_Lnsp_233.jpg
561 ms
k2.items.cache.43b5d7ea76b81555b1a0c02c96d35f9e_Lnsp_233.jpg
569 ms
k2.items.cache.d02ff631f43a07d2bbd6a624d138cae9_Lnsp_233.jpg
589 ms
k2.items.cache.4aeceb4858a40a58946f4bde4f271abb_Lnsp_233.jpg
642 ms
k2.items.cache.09005e86c53174509703527f394e38f9_Lnsp_233.jpg
650 ms
k2.items.cache.096f6eb0ac11cd6cb055833c55a92577_Lnsp_233.jpg
652 ms
k2.items.cache.ca7bf19fbc3dba58b73409bf27a5af10_Lnsp_233.jpg
655 ms
k2.items.cache.66a481072e01b0cbd3ec8d4838e70a69_Lnsp_233.jpg
671 ms
8135fc565070315d12fae16f2fe25796_M.jpg
809 ms
9b942c8b3b0e818f2b9f830bc8ebd648_M.jpg
723 ms
5817eff55236b67dee6dd7db39c5167e_M.jpg
814 ms
pubads_impl_81.js
15 ms
ads
84 ms
container.html
24 ms
__utm.gif
16 ms
7eebf35d67cf5ee0f6f958663b4a3774_M.jpg
725 ms
2273e93d970f5fa5c488f649b5600d1c_M.jpg
644 ms
ec514a0870ba50337696f4df0fd17ab8_M.jpg
658 ms
e698483d2e6511ca3634ffc7629a08c2_M.jpg
709 ms
storageframe.html
29 ms
b17aa629c33bedaea37aa0d65212d4ed_M.jpg
669 ms
65051f11f7e5efd0b9b78a252bca070a_M.jpg
764 ms
2060864052194013899
29 ms
62f4ae92849d28369f0c1b400f2a3bf4_M.jpg
722 ms
osd.js
8 ms
2d33cfacc88e7b7e640c70a5fa29bb5c_M.jpg
729 ms
m
24 ms
761e66c60b82c5459ca9ca7f18aca011_M.jpg
721 ms
tool-dept-payment.jpg
671 ms
ae2ff73e75777a2ff9d0569f3fc05715_M.jpg
756 ms
25bc321c36c6eec9d04f2092c18efa5f_M.jpg
717 ms
8bd609062add694c516a3c09734e5da3_M.jpg
669 ms
f04c6ec7cff7942c8fc2acdf978cabf6_M.jpg
672 ms
nsp_portal_mode_2_interface.png
665 ms
nr-768.min.js
29 ms
nsp_portal_mode_2_img.png
85 ms
cbff59f3e6
53 ms
fpress.gr accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
The document uses <meta http-equiv="refresh">
fpress.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
Page has valid source maps
fpress.gr SEO score
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 Fpress.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 Fpress.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.
fpress.gr
Open Graph description is not detected on the main page of Fpress. 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: