Tools & Wizards About Us
gimbe.org screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

gimbe.org

GIMBE

Page Load Speed

4.4 sec in total

First Response

1.4 sec

Resources Loaded

2.8 sec

Page Rendered

201 ms

gimbe.org screenshot

About Website

Click here to check amazing GIMBE content for Italy. Otherwise, check out these important facts you probably never knew about gimbe.org

La Fondazione GIMBE è un’organizzazione indipendente che dal 1996 promuove l’integrazione delle migliori evidenze scientifiche in tutte le decisioni politiche, manageriali, professionali che riguardan...

Visit gimbe.org

Key Findings

We analyzed Gimbe.org page load time and found that the first response time was 1.4 sec and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

gimbe.org performance score

0

Network Requests Diagram

gimbe.org

1411 ms

style.css

267 ms

jquery.jscrollpane.css

263 ms

prettyPhoto.css

276 ms

function.js

279 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 90% of them (47 requests) were addressed to the original Gimbe.org, 4% (2 requests) were made to Google-analytics.com and 2% (1 request) were made to Downloads.mailchimp.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Gimbe.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 515.0 kB (39%)

Content Size

1.3 MB

After Optimization

820.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gimbe.org main page is 1.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. 40% of websites need less resources to load. Images take 763.9 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 35.8 kB

  • Original 43.4 kB
  • After minification 37.0 kB
  • After compression 7.7 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 6.5 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 35.8 kB or 82% of the original size.

Image Optimization

-6%

Potential reduce by 46.4 kB

  • Original 763.9 kB
  • After minification 717.5 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. GIMBE images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 312.3 kB

  • Original 390.6 kB
  • After minification 237.5 kB
  • After compression 78.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 312.3 kB or 80% of the original size.

CSS Optimization

-88%

Potential reduce by 120.5 kB

  • Original 137.1 kB
  • After minification 117.6 kB
  • After compression 16.6 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. Gimbe.org needs all CSS files to be minified and compressed as it can save up to 120.5 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 32 (63%)

Requests Now

51

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of GIMBE. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

gimbe.org

gimbe.org

1411 ms

style.css

style.css

267 ms

jquery.jscrollpane.css

jquery.jscrollpane.css

263 ms

prettyPhoto.css

prettyPhoto.css

276 ms

function.js

function.js

279 ms

jquery-1.7.1.js

jquery-1.7.1.js

585 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

290 ms

jquery.infinitecarousel3.js

jquery.infinitecarousel3.js

345 ms

http_request.js

http_request.js

346 ms

jquery.jscrollpane.js

jquery.jscrollpane.js

367 ms

jquery.mousewheel.js

jquery.mousewheel.js

366 ms

cookiechoices.js

cookiechoices.js

87 ms

ga.js

ga.js

55 ms

goal.min.js

goal.min.js

59 ms

hdot.gif

hdot.gif

87 ms

Position_statement_GIMBE_Screening_onclogici_2015.jpg

Position_statement_GIMBE_Screening_onclogici_2015.jpg

545 ms

HONConduct947214_s2.gif

HONConduct947214_s2.gif

201 ms

bg_body.jpg

bg_body.jpg

105 ms

hdot.gif

hdot.gif

91 ms

angolosx.gif

angolosx.gif

97 ms

angolodx.gif

angolodx.gif

92 ms

visore.jpg

visore.jpg

171 ms

conferenza2016_report_primopiano.jpg

conferenza2016_report_primopiano.jpg

679 ms

conferenza2016_premi_primopiano2.jpg

conferenza2016_premi_primopiano2.jpg

590 ms

conferenza2016_aifa_primopiano.jpg

conferenza2016_aifa_primopiano.jpg

542 ms

conferenza2016_salviamoSSN_primopiano.jpg

conferenza2016_salviamoSSN_primopiano.jpg

548 ms

conferenza2016_borsa_primopiano.jpg

conferenza2016_borsa_primopiano.jpg

202 ms

sostieni-la-fondazione-gimbe-cuore.jpg

sostieni-la-fondazione-gimbe-cuore.jpg

421 ms

org_hp_edu.jpg

org_hp_edu.jpg

335 ms

Salviamo_SSN_home_dx2.jpg

Salviamo_SSN_home_dx2.jpg

419 ms

registrazione_form_1.php

registrazione_form_1.php

175 ms

network_dx.gif

network_dx.gif

248 ms

network_btn.gif

network_btn.gif

347 ms

network_sx.gif

network_sx.gif

444 ms

container_top.gif

container_top.gif

455 ms

GIMBEORG.jpg

GIMBEORG.jpg

542 ms

header_menu_separa.gif

header_menu_separa.gif

539 ms

menu_bg.jpg

menu_bg.jpg

580 ms

hp_ico_evidence.gif

hp_ico_evidence.gif

587 ms

hp_ico_education.gif

hp_ico_education.gif

622 ms

hp_ico_ebch_library.gif

hp_ico_ebch_library.gif

624 ms

palletto1_library.gif

palletto1_library.gif

638 ms

container_bottom.gif

container_bottom.gif

671 ms

footer_separa.gif

footer_separa.gif

677 ms

home_gimbe_dot_on.gif

home_gimbe_dot_on.gif

706 ms

home_gimbe_dot_off.gif

home_gimbe_dot_off.gif

707 ms

sfondo_trasp.png

sfondo_trasp.png

130 ms

controls.png

controls.png

184 ms

__utm.gif

__utm.gif

12 ms

style.css

style.css

88 ms

registrazione_functions.js

registrazione_functions.js

93 ms

org_avanti.gif

org_avanti.gif

87 ms

SEO Factors

gimbe.org SEO score

0

Language and Encoding

  • Language Detected

    IT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Gimbe.org can be misinterpreted by Google and other search engines. Our service has detected that Italian 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 Gimbe.org 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.

Social Sharing Optimization

gimbe.org

Open Graph description is not detected on the main page of GIMBE. 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: