3 sec in total
230 ms
2.5 sec
290 ms
Click here to check amazing Exploratorium content. Otherwise, check out these important facts you probably never knew about exploratorium.com
Experience the Exploratorium. Let your curiosity roam free through hundreds of exhibits in our six spacious indoor and outdoor galleries at Pier 15, San Francisco.
Visit exploratorium.comWe analyzed Exploratorium.com page load time and found that the first response time was 230 ms and then it took 2.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
exploratorium.com performance score
230 ms
276 ms
144 ms
150 ms
149 ms
Our browser made a total of 114 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Exploratorium.com, 14% (16 requests) were made to and 4% (4 requests) were made to Scontent.cdninstagram.com. The less responsive or slowest element that took the longest time to load (660 ms) relates to the external source Exploratorium.edu.
Page size can be reduced by 1.8 MB (56%)
3.1 MB
1.4 MB
In fact, the total size of Exploratorium.com main page is 3.1 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. Javascripts take 1.8 MB which makes up the majority of the site volume.
Potential reduce by 200.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. 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 200.7 kB or 77% of the original size.
Potential reduce by 81.7 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. Exploratorium images are well optimized though.
Potential reduce by 1.4 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.4 MB or 76% of the original size.
Potential reduce by 107.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. Exploratorium.com needs all CSS files to be minified and compressed as it can save up to 107.7 kB or 83% of the original size.
Number of requests can be reduced by 69 (72%)
96
27
The browser has sent 96 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Exploratorium. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 45 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
www.exploratorium.edu
230 ms
zky1mem.js
276 ms
css_xE-rWrJf-fncB6ztZfd2huxqgxu4WO-qwma6Xer30m4.css
144 ms
css_wopObPmPKhp9cY2QbpKp2u7mlNcVFBQTmjG2vrzt164.css
150 ms
css_HwKew1yO73eWjGLa9WD9eIuIti-iuKB_U5KzlPZ4y9Y.css
149 ms
css_wbSj8nRm9OG-31Z5cMrQHKiicAzVg-e4qQzQSqzsjt0.css
151 ms
jquery.js
224 ms
jquery.once.js
152 ms
drupal.js
215 ms
jquery.colorbox-min.js
221 ms
colorbox.js
221 ms
colorbox_style.js
223 ms
colorbox_inline.js
224 ms
custom_search.js
291 ms
sfsmallscreen.js
294 ms
jquery.hoverIntent.minified.js
294 ms
sftouchscreen.js
293 ms
supposition.js
295 ms
jquery.bgiframe.min.js
294 ms
superfish.js
360 ms
supersubs.js
366 ms
superfish.js
367 ms
mobile-menu.js
367 ms
slideshows_init.js
367 ms
media-object-collection-scripts.js
368 ms
jquery-1.10.2.js
579 ms
jquery-ui.js
660 ms
jquery110-noconflict.js
439 ms
accordion-init.js
438 ms
views-better-exposed-taxonomies.js
440 ms
jquery-1.11.0.min.js
512 ms
jquery-migrate-1.2.1.min.js
513 ms
slick.min.js
512 ms
jquery111-noconflict.js
512 ms
jquery-2.1.1.min.js
592 ms
justifiedGallery.js
593 ms
jquery.colorbox.js
593 ms
BrightcoveExperiences.js
30 ms
index.min.js
87 ms
get
15 ms
themes.css
534 ms
responsiveslides.css
520 ms
socialriver.css
584 ms
homepage.css
587 ms
jquery211-noconflict.js
581 ms
responsiveslides.min.js
584 ms
instafeed.min.js
601 ms
d
191 ms
explo-logo-black.svg
79 ms
eclipse2016-960x380.jpg
481 ms
AllEyesOnYou.jpg
200 ms
education-slide.jpg
473 ms
new_banner.jpg
210 ms
sos-graphic-banner-960x380.jpg
81 ms
gala2016-pod.jpg
206 ms
afterparty2016.jpg
209 ms
ad-fade-pod-march17.jpg
211 ms
tactile-dome-banner.jpg
474 ms
explorablespod.jpg
473 ms
totalpod.jpg
473 ms
snackspod.jpg
473 ms
spectrum-pod.jpg
478 ms
Sos_Activity_pod.jpg
475 ms
facebook.png
474 ms
instagram.png
475 ms
twitter.png
475 ms
youtube.png
477 ms
tumblr.png
478 ms
foursquare.png
477 ms
p.gif
121 ms
gtm.js
120 ms
mobile-menu-button.gif
283 ms
explo-logo-white.svg
283 ms
search_submit_icon.jpg
285 ms
arrow_white_solid.png
285 ms
I8lO+Rxwo88VShZ5574aVXXnvjrXfe++CjT78AbtduqQAAAA==
26 ms
AG7XbqkAAAA=
25 ms
I8lO+Rxwo88VShZ5574aVXXnvjrXfe++CjT78AbtduqQAAAA==
25 ms
A+F9HHLYEUcdc9wJJ51y2hln5TjnvAsuuuSyK6665robbrrldnhjd92T674H8jyU75HHCjzxVKFnnnvhpVdee+Otd9774KNPvwBu126pAAAA
24 ms
A+F9HHLYEUcdc9wJJ51y2hln5TjnvAsuuuSyK6665robbrrldnhjd92T674H8jyU75HHCjzxVKFnnnvhpVdee+Otd9774KNPvwBu126pAAAA
22 ms
I8lO+Rxwo88VShZ5574aVXXnvjrXfe++CjT78AbtduqQAAAA==
22 ms
dx0CGHHXHUMcedcNIpp51x1jnnXXDRJZddcdU11+W64aZb4Y3dcdc9ee57IF+Bhwo9UuSxJ5565rkXXnrltTfeeue9Dz7+BIlfbrUAAAA=
21 ms
dx0CGHHXHUMcedcNIpp51x1jnnXXDRJZddcdU11+W64aZb4Y3dcdc9ee57IF+Bhwo9UuSxJ5565rkXXnrltTfeeue9Dz7+BIlfbrUAAAA=
20 ms
dx0CGHHXHUMcedcNIpp51x1jnnXXDRJZddcdU11+W64aZb4Y3dcdc9ee57IF+Bhwo9UuSxJ5565rkXXnrltTfeeue9Dz7+BIlfbrUAAAA=
19 ms
t9thp11222OvffaH93HQIYcdcdQxx51w0imnnXHWOeddcNEll11x1TXX5brhplvhjd1x1z157nsgX4GHCj1S5LEnnnrmuRdeeuW1N956570PPv4EiV9utQAAAA==
19 ms
gSJX261AAAA
19 ms
t9thp11222OvffaH93HQIYcdcdQxx51w0imnnXHWOeddcNEll11x1TXX5brhplvhjd1x1z157nsgX4GHCj1S5LEnnnrmuRdeeuW1N956570PPv4EiV9utQAAAA==
17 ms
gSJX261AAAA
17 ms
dx0CGHHXHUMcedcNIpp51x1jnnXXDRJZddcdU11+W64aZb4Y3dcdc9ee57IF+Bhwo9UuSxJ5565rkXXnrltTfeeue9Dz7+BIlfbrUAAAA=
17 ms
t9thp11222OvffaH93HQIYcdcdQxx51w0imnnXHWOeddcNEll11x1TXX5brhplvhjd1x1z157nsgX4GHCj1S5LEnnnrmuRdeeuW1N956570PPv4EiV9utQAAAA==
15 ms
dx0CGHHXHUMcedcNIpp51x1jnnXXDRJZddcdU11+W64aZb4Y3dcdc9ee57IF+Bhwo9UuSxJ5565rkXXnrltTfeeue9Dz7+BIlfbrUAAAA=
15 ms
analytics.js
55 ms
8044.js
55 ms
162 ms
fbds.js
53 ms
oct.js
52 ms
linkid.js
15 ms
158 ms
adsct
209 ms
adsct
162 ms
collect
148 ms
recent
306 ms
notice
220 ms
slideshow-arrows-black.png
99 ms
s
35 ms
collect
62 ms
u
54 ms
img
16 ms
truste_logo_small.png
311 ms
929328_197170753988482_985555120_n.jpg
20 ms
12822579_550167078480330_809211377_n.jpg
24 ms
12751083_1524257134543386_1983888530_n.jpg
25 ms
12797953_664598397014737_1836000448_n.jpg
26 ms
4 ms
exploratorium.com SEO score
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Exploratorium.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Exploratorium.com 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.
exploratorium.com
Open Graph description is not detected on the main page of Exploratorium. 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: