13.2 sec in total
258 ms
7.8 sec
5.1 sec
Visit zion.net now to see the best up-to-date ZION content and also check out these interesting facts you probably never knew about zion.net
Visit zion.netWe analyzed Zion.net page load time and found that the first response time was 258 ms and then it took 12.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
zion.net performance score
name
value
score
weighting
Value5.9 s
4/100
10%
Value10.3 s
0/100
25%
Value11.1 s
6/100
10%
Value590 ms
50/100
30%
Value0.023
100/100
15%
Value14.1 s
9/100
10%
258 ms
2044 ms
296 ms
357 ms
180 ms
Our browser made a total of 63 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Zion.net, 94% (59 requests) were made to Zion.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (4.7 sec) relates to the external source Zion.com.
Page size can be reduced by 387.8 kB (18%)
2.2 MB
1.8 MB
In fact, the total size of Zion.net main page is 2.2 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. 35% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.
Potential reduce by 108.8 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 108.8 kB or 80% of the original size.
Potential reduce by 28.4 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. ZION images are well optimized though.
Potential reduce by 56.4 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 56.4 kB or 68% of the original size.
Potential reduce by 194.1 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. Zion.net needs all CSS files to be minified and compressed as it can save up to 194.1 kB or 87% of the original size.
Number of requests can be reduced by 22 (36%)
61
39
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of ZION. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 14 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
zion.net
258 ms
www.zion.com
2044 ms
wp-emoji-release.min.js
296 ms
style.min.css
357 ms
theme.min.css
180 ms
styles.css
180 ms
css
39 ms
style.css
428 ms
blocks.css
457 ms
jquery.js
654 ms
jquery-migrate.min.js
497 ms
owl.carousel.css
328 ms
sa-owl-theme.css
344 ms
animate.min.css
453 ms
magnific-popup.css
344 ms
scripts.js
512 ms
api.js
110 ms
skip-link-focus-fix.js
480 ms
navigation.js
605 ms
global.js
642 ms
jquery.scrollTo.js
1003 ms
wp-embed.min.js
705 ms
owl.carousel.min.js
892 ms
jquery.magnific-popup.min.js
940 ms
owl.carousel2.thumbs.min.js
779 ms
cropped-istock-838296470-web.jpg
1487 ms
cropped-zion.png
1334 ms
iStock-843016322-2000x1200.jpg
1787 ms
iStock-664035840-2000x1200.jpg
2712 ms
istock-832109622-web-2000x1200.jpg
3382 ms
Zion_Client1.png
2411 ms
Zion_Client2.png
2521 ms
Zion_Client3.png
2412 ms
Zion_Client4.png
2414 ms
Zion_Client5.png
2653 ms
Zion_Client6.png
2651 ms
GaleInteractive_HumanAnatomny-150x150.png
2796 ms
GaleInteractive_HumanAnatomy_Dashboard.jpg
2931 ms
GaleInteractive_HumanAnatomy_Activities.jpg
3067 ms
GaleInteractive_HumanAnatomy_Activity.jpg
3075 ms
GaleInteractive_HumanAnatomy_Activity_FullScreen.jpg
3124 ms
GaleInteractive_Science-150x150.png
3153 ms
GaleInteractive_Science_Dashboard.jpg
3290 ms
GaleInteractive_Science_Activities.jpg
3469 ms
GaleInteractive_Science_Activity.jpg
3495 ms
GaleInteractive_Science_Activity_FullScreen.jpg
3517 ms
GaleInteractive_Chemistry-150x150.png
3643 ms
GaleInteractive_Chemistry_Dashboard.jpg
3730 ms
GaleInteractive_Chemistry_Activities.jpg
4680 ms
GaleInteractive_Chemistry_Activity.jpg
3826 ms
GaleInteractive_Chemistry_Activity_FullScreen.jpg
3836 ms
MyCigna-150x150.png
3607 ms
Zion_Mobile1-150x150.png
3786 ms
recaptcha__en.js
27 ms
Zion_Mobile2-150x150.png
3910 ms
Zipcar_Small-150x150.png
3754 ms
ZipcarApp1.jpg
3862 ms
ZipcarApp2.jpg
3779 ms
ZipcarApp3.jpg
3860 ms
MapLocations-300x169.jpg
3748 ms
iStock-475684294-web-2000x1200.jpg
4016 ms
lightbox_zoom.png
3143 ms
ajax-loader.gif
3116 ms
zion.net accessibility score
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
Buttons do not have an accessible name
zion.net 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
zion.net SEO score
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 Zion.net 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 Zion.net 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.
zion.net
Open Graph description is not detected on the main page of ZION. 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: