3.8 sec in total
251 ms
3.1 sec
458 ms
Click here to check amazing Chrono Zoom content for United States. Otherwise, check out these important facts you probably never knew about chronozoom.com
ChronoZoom is an open-source community project dedicated to visualizing the history of everything.
Visit chronozoom.comWe analyzed Chronozoom.com page load time and found that the first response time was 251 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.
chronozoom.com performance score
name
value
score
weighting
Value3.8 s
26/100
10%
Value13.1 s
0/100
25%
Value10.9 s
6/100
10%
Value660 ms
45/100
30%
Value1.456
0/100
15%
Value16.4 s
5/100
10%
251 ms
17 ms
104 ms
207 ms
59 ms
Our browser made a total of 83 requests to load all elements on the main page. We found that 86% of them (71 requests) were addressed to the original Chronozoom.com, 5% (4 requests) were made to Cdnjs.cloudflare.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (669 ms) belongs to the original domain Chronozoom.com.
Page size can be reduced by 301.5 kB (42%)
717.2 kB
415.7 kB
In fact, the total size of Chronozoom.com main page is 717.2 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 50% of websites need less resources to load. Javascripts take 311.6 kB which makes up the majority of the site volume.
Potential reduce by 61.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 12.9 kB, which is 17% 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 61.6 kB or 83% of the original size.
Potential reduce by 30.1 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, Chrono Zoom needs image optimization as it can save up to 30.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 163.0 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 163.0 kB or 52% of the original size.
Potential reduce by 46.8 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. Chronozoom.com needs all CSS files to be minified and compressed as it can save up to 46.8 kB or 79% of the original size.
Number of requests can be reduced by 31 (39%)
80
49
The browser has sent 80 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Chrono Zoom. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
chronozoom.com
251 ms
ga.js
17 ms
jquery-1.7.2.min.js
104 ms
airbrake-shim.js
207 ms
jquery-ui.min.js
59 ms
modernizr-2.0.6-development-only.js
134 ms
wl.js
62 ms
jquery.cookie.min.js
62 ms
rx.js
371 ms
rx.jQuery.js
273 ms
jquery.mousewheel.min.js
63 ms
csvToArray.v2.1.js
306 ms
ACS.js
385 ms
seadragon-min.js
545 ms
jquery.dotdotdot.min.js
62 ms
audio.min.js
405 ms
jquery.autonumeric-1.9.24.min.js
492 ms
marked.min.js
61 ms
spectrum.min.js
557 ms
jquery.nouislider.min.js
669 ms
FileSaver.min.js
632 ms
__utm.gif
16 ms
search-icon.png
226 ms
profile-icon.png
164 ms
wait.gif
264 ms
edit.svg
158 ms
close_off.png
204 ms
msr.png
219 ms
ucb.png
312 ms
msu.png
378 ms
github.png
382 ms
cz.min.css
447 ms
spectrum.min.css
404 ms
jquery.nouislider.min.css
355 ms
cz.merged.min.js
611 ms
css
76 ms
chronozoom.png
180 ms
defaultGradientBox.jpg
202 ms
bing-mediapicker.html
242 ms
canedit
92 ms
linen.jpg
213 ms
header-edit-form.html
146 ms
auth-edit-timeline-form.html
150 ms
auth-edit-exhibit-form.html
153 ms
auth-edit-contentitem-form.html
182 ms
contentitem-listbox.html
144 ms
header-edit-profile-form.html
189 ms
header-login-form.html
297 ms
auth-edit-tour-form.html
253 ms
tourstop-listbox.html
263 ms
tourslist-form.html
239 ms
tour-listbox.html
312 ms
timeseries-graph-form.html
321 ms
timeseries-data-form.html
344 ms
message-window.html
348 ms
header-search-form.html
356 ms
header-session-expired-form.html
382 ms
tour-caption-form.html
408 ms
mediapicker-form.html
414 ms
overlay.html
458 ms
auth-edit-collection-form.html
485 ms
auth-edit-collection-editors.html
481 ms
info
458 ms
collections
501 ms
chronozoom.com
421 ms
loading.gif
540 ms
SkyDrive-Import-50X150.png
436 ms
Temp-Thumbnail2.png
345 ms
icon_twitter.svg
342 ms
star.svg
183 ms
featured.json
186 ms
user
185 ms
user
231 ms
background.jpg
397 ms
data
95 ms
tile-bighistory.jpg
233 ms
fallbackWalterImageDefault.jpg
304 ms
tile-aidsquilt.jpg
225 ms
tile-cern.jpg
294 ms
tile-chinesemedicine.jpg
334 ms
tile-nobel.jpg
469 ms
select.png
424 ms
airbrake.min.js
94 ms
chronozoom.com accessibility score
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
chronozoom.com 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
Browser errors were logged to the console
Page has valid source maps
chronozoom.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Chronozoom.com can be misinterpreted by Google and other search engines. Our service has detected that English 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 Chronozoom.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.
chronozoom.com
Open Graph description is not detected on the main page of Chrono Zoom. 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: