5.1 sec in total
870 ms
3.9 sec
316 ms
Click here to check amazing Explora content for United States. Otherwise, check out these important facts you probably never knew about explora.us
Explora is an innovative experiential learning center located in the heart of Old Town Albuquerque.
Visit explora.usWe analyzed Explora.us page load time and found that the first response time was 870 ms and then it took 4.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.
explora.us performance score
name
value
score
weighting
Value6.2 s
3/100
10%
Value8.8 s
1/100
25%
Value9.2 s
13/100
10%
Value3,880 ms
1/100
30%
Value0.093
91/100
15%
Value18.1 s
3/100
10%
870 ms
111 ms
111 ms
166 ms
169 ms
Our browser made a total of 113 requests to load all elements on the main page. We found that 47% of them (53 requests) were addressed to the original Explora.us, 13% (15 requests) were made to Maps.google.com and 8% (9 requests) were made to Calendar.google.com. The less responsive or slowest element that took the longest time to load (948 ms) belongs to the original domain Explora.us.
Page size can be reduced by 1.0 MB (54%)
1.9 MB
867.8 kB
In fact, the total size of Explora.us main page is 1.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. 65% of websites need less resources to load. Javascripts take 1.1 MB which makes up the majority of the site volume.
Potential reduce by 73.1 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 21.6 kB, which is 25% 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 73.1 kB or 83% of the original size.
Potential reduce by 164.0 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. Obviously, Explora needs image optimization as it can save up to 164.0 kB or 26% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 706.5 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 706.5 kB or 66% of the original size.
Potential reduce by 84.9 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. Explora.us needs all CSS files to be minified and compressed as it can save up to 84.9 kB or 81% of the original size.
Number of requests can be reduced by 60 (59%)
102
42
The browser has sent 102 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Explora. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 31 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
870 ms
grid-12.css
111 ms
gantry.css
111 ms
joomla.css
166 ms
template.css
169 ms
typography.css
113 ms
rokstories.css
150 ms
fusionmenu.css
220 ms
mootools-core.js
386 ms
core.js
223 ms
mootools-more.js
527 ms
jquery.min.js
32 ms
jquery.lazyload.js
274 ms
caption.js
274 ms
gantry-smartload.js
327 ms
browser-engines.js
340 ms
rokstories.js
381 ms
fusion.js
438 ms
maps
34 ms
css
24 ms
ga.js
45 ms
shadow.png
92 ms
bottom-shadow.png
218 ms
content-background.png
223 ms
dome.png
290 ms
logo.png
165 ms
give-now.png
164 ms
search-box.png
172 ms
searchButton.gif
222 ms
menuBackground.png
248 ms
level1Bg-green.png
288 ms
menutop-daddy.png
368 ms
CampExtraweek_3pixTexturePurple_JPG_webslide_thumb.jpg
368 ms
exhibits-heading.png
368 ms
mat_exh_041012_16605re%20cc.jpg
456 ms
watch-video.png
398 ms
video-photo.jpg
455 ms
shop-heading.png
489 ms
Web-store_Highlight-RC_store_6405.jpg
670 ms
information-en.png
509 ms
FB-f-Logo__blue_29.png
573 ms
TwitterLogo_55acee.png
632 ms
white-small-circle.png
574 ms
e-news-icon-paper-airplane.png
669 ms
white-small-circle.png
725 ms
embed
137 ms
arrows.png
697 ms
orange-arrow.png
697 ms
dotted-line.png
764 ms
left-bottom-shadow-small.png
766 ms
right-bottom-shadow-small.png
766 ms
module-gradient.png
767 ms
circles_s1.png
768 ms
k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf
50 ms
cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf
49 ms
__utm.gif
74 ms
187TYb8ysVvxar86IcDsZ_esZW2xOQ-xsNqO47m55DA.ttf
67 ms
banner-background-image._CB309675353_.png
72 ms
blank.gif
664 ms
spinner.gif
730 ms
CampExtraweek_3pixTexturePurple_JPG_webslide.jpg
804 ms
embed
72 ms
0992f33945a94632a64d2587cfa6f814embedcompiled_fastui.css
5 ms
0992f33945a94632a64d2587cfa6f814embedcompiled__en.js
23 ms
client.js
80 ms
cb=gapi.loaded_0
10 ms
postmessageRelay
34 ms
3193398744-postmessagerelay.js
23 ms
rpc:shindig_random.js
31 ms
cb=gapi.loaded_0
6 ms
logo-plus.png
26 ms
googlelogo_color_46x16dp.png
37 ms
proxy.html
49 ms
blank.gif
27 ms
menu_arrow_open.gif
15 ms
icon_print.gif
18 ms
btn_menu6.gif
23 ms
combined_v22.png
32 ms
cb=gapi.loaded_0
5 ms
events
179 ms
common.js
11 ms
map.js
11 ms
overlay.js
10 ms
util.js
59 ms
marker.js
58 ms
StaticMapService.GetMapImage
95 ms
onion.js
23 ms
openhand_8_8.cur
48 ms
none
948 ms
ViewportInfoService.GetViewportInfo
38 ms
stats.js
35 ms
controls.js
31 ms
infowindow.js
49 ms
transparent.png
37 ms
css
27 ms
google4.png
50 ms
mapcnt6.png
35 ms
sv5.png
36 ms
vt
36 ms
vt
31 ms
vt
93 ms
vt
29 ms
vt
20 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
15 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
15 ms
Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf
17 ms
d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf
17 ms
tmapctrl.png
60 ms
cb_scout5.png
77 ms
tmapctrl4.png
77 ms
marker.png
78 ms
AuthenticationService.Authenticate
13 ms
737 ms
explora.us 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
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
explora.us best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
explora.us SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Explora.us 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 Explora.us 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.
explora.us
Open Graph description is not detected on the main page of Explora. 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: