Tools & Wizards About Us
museu.gulbenkian.pt screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

museu.gulbenkian.pt

Museu Calouste Gulbenkian

Page Load Speed

2.7 sec in total

First Response

279 ms

Resources Loaded

2.1 sec

Page Rendered

353 ms

museu.gulbenkian.pt screenshot

About Website

Visit museu.gulbenkian.pt now to see the best up-to-date Museu Gulbenkian content for Portugal and also check out these interesting facts you probably never knew about museu.gulbenkian.pt

O Museu Calouste Gulbenkian tem duas coleções de arte - Coleção do Fundador e Coleção Moderna - e uma extensa programação de exposições temporárias.

Visit museu.gulbenkian.pt

Key Findings

We analyzed Museu.gulbenkian.pt page load time and found that the first response time was 279 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

museu.gulbenkian.pt performance score

0

Network Requests Diagram

museu.gulbenkian.pt

279 ms

Inicio

168 ms

ajaxLoad.js

114 ms

jquery.1.7.1.min.js

131 ms

submission.js

149 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 86% of them (48 requests) were addressed to the original Museu.gulbenkian.pt, 11% (6 requests) were made to Gulbenkian.mediadepo.net and 4% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1 sec) belongs to the original domain Museu.gulbenkian.pt.

Page Optimization Overview & Recommendations

Page size can be reduced by 732.8 kB (10%)

Content Size

7.5 MB

After Optimization

6.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Museu.gulbenkian.pt main page is 7.5 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. 30% of websites need less resources to load. Images take 6.9 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 35.5 kB

  • Original 43.9 kB
  • After minification 39.7 kB
  • After compression 8.4 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 35.5 kB or 81% of the original size.

Image Optimization

-4%

Potential reduce by 282.0 kB

  • Original 6.9 MB
  • After minification 6.6 MB

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. Museu Gulbenkian images are well optimized though.

JavaScript Optimization

-70%

Potential reduce by 347.1 kB

  • Original 494.4 kB
  • After minification 477.3 kB
  • After compression 147.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 347.1 kB or 70% of the original size.

CSS Optimization

-83%

Potential reduce by 68.2 kB

  • Original 82.5 kB
  • After minification 67.6 kB
  • After compression 14.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. Museu.gulbenkian.pt needs all CSS files to be minified and compressed as it can save up to 68.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (56%)

Requests Now

52

After Optimization

23

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

museu.gulbenkian.pt

museu.gulbenkian.pt

279 ms

Inicio

Inicio

168 ms

ajaxLoad.js

ajaxLoad.js

114 ms

jquery.1.7.1.min.js

jquery.1.7.1.min.js

131 ms

submission.js

submission.js

149 ms

getObject.php

getObject.php

329 ms

seed3.js

seed3.js

158 ms

jquery-ui-1.8.16.custom.min.js

jquery-ui-1.8.16.custom.min.js

171 ms

reset.css

reset.css

166 ms

jquery-ui-1.10.1.custom.css

jquery-ui-1.10.1.custom.css

248 ms

shadowbox.css

shadowbox.css

171 ms

ss3_main.css

ss3_main.css

172 ms

ss3_main.css

ss3_main.css

192 ms

960_fluid.css

960_fluid.css

193 ms

base_new.css

base_new.css

344 ms

css3-mediaqueries.js

css3-mediaqueries.js

249 ms

jquery.cycle2.js

jquery.cycle2.js

349 ms

jquery.cycle2.carousel.min.js

jquery.cycle2.carousel.min.js

282 ms

jquery.masonry.3.min.js

jquery.masonry.3.min.js

370 ms

jquery.slideViewerPro.1.5.js

jquery.slideViewerPro.1.5.js

342 ms

jquery.pajinate.js

jquery.pajinate.js

347 ms

superfish.js

superfish.js

374 ms

jquery.zoom.js

jquery.zoom.js

408 ms

shadowbox.js

shadowbox.js

497 ms

custom_museu.js

custom_museu.js

410 ms

mainMenu_bg.png

mainMenu_bg.png

139 ms

FCG_PartyLogo.jpg

FCG_PartyLogo.jpg

138 ms

logo_museu.png

logo_museu.png

139 ms

friso_PC1.jpg

friso_PC1.jpg

979 ms

friso_galerias7.jpg

friso_galerias7.jpg

737 ms

fw_pop1.jpg

fw_pop1.jpg

734 ms

friso_expo1.jpg

friso_expo1.jpg

972 ms

friso_google.jpg

friso_google.jpg

649 ms

estaque_PC1.jpg

estaque_PC1.jpg

464 ms

fw_ca1.jpg

fw_ca1.jpg

574 ms

marfins1.jpg

marfins1.jpg

761 ms

as8.jpg

as8.jpg

746 ms

gal2.jpg

gal2.jpg

827 ms

g1.jpg

g1.jpg

829 ms

ajax-loader.gif

ajax-loader.gif

831 ms

header_bg.png

header_bg.png

853 ms

search_btn.png

search_btn.png

897 ms

OpenSans-Regular-webfont.woff

OpenSans-Regular-webfont.woff

894 ms

questrial-regular-webfont.woff

questrial-regular-webfont.woff

903 ms

loading.gif

loading.gif

954 ms

headingLine_white.png

headingLine_white.png

963 ms

headingLine_black.png

headingLine_black.png

966 ms

controlBar_btn.png

controlBar_btn.png

972 ms

headingLine.png

headingLine.png

992 ms

icon_movieclip.png

icon_movieclip.png

1020 ms

icons_social.png

icons_social.png

1020 ms

analytics.js

analytics.js

76 ms

single=0&date=1458086400&nocache=1

single=0&date=1458086400&nocache=1

994 ms

calendar_slide.png

calendar_slide.png

951 ms

collect

collect

18 ms

base_print.css

base_print.css

88 ms

SEO Factors

museu.gulbenkian.pt SEO score

0

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

museu.gulbenkian.pt

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