2.7 sec in total
236 ms
2 sec
547 ms
Click here to check amazing Zooo content. Otherwise, check out these important facts you probably never knew about zooo.be
3d visualization site in the fields of activities such as architecture, real estate development, mobility, urban planning and event management.
Visit zooo.beWe analyzed Zooo.be page load time and found that the first response time was 236 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
zooo.be performance score
name
value
score
weighting
Value1.7 s
93/100
10%
Value14.2 s
0/100
25%
Value3.2 s
92/100
10%
Value40 ms
100/100
30%
Value0.127
82/100
15%
Value2.6 s
98/100
10%
236 ms
98 ms
20 ms
37 ms
197 ms
Our browser made a total of 69 requests to load all elements on the main page. We found that 90% of them (62 requests) were addressed to the original Zooo.be, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (902 ms) belongs to the original domain Zooo.be.
Page size can be reduced by 148.3 kB (9%)
1.7 MB
1.5 MB
In fact, the total size of Zooo.be main page is 1.7 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. 50% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by -8 B
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 web page is already compressed.
Potential reduce by 41.3 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. Zooo images are well optimized though.
Potential reduce by 89.9 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 89.9 kB or 59% of the original size.
Potential reduce by 17.2 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. Zooo.be needs all CSS files to be minified and compressed as it can save up to 17.2 kB or 82% of the original size.
Number of requests can be reduced by 3 (5%)
65
62
The browser has sent 65 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zooo. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 4 to 1 for JavaScripts and as a result speed up the page load time.
home-3D-en.html
236 ms
zoooooo.css
98 ms
css
20 ms
css
37 ms
jquery-1.11.1.min.js
197 ms
jquery.customSelect.min.js
194 ms
isotope.pkgd.min.js
196 ms
ga.js
8 ms
header.png
132 ms
zooo_EN.png
191 ms
facebook_picto.png
193 ms
linkedin_picto.png
194 ms
grid_button.png
193 ms
marker.png
194 ms
fleche.png
194 ms
timthumb.php
484 ms
play.png
290 ms
timthumb.php
390 ms
360.png
291 ms
timthumb.php
297 ms
timthumb.php
392 ms
timthumb.php
483 ms
timthumb.php
678 ms
timthumb.php
397 ms
timthumb.php
491 ms
timthumb.php
493 ms
timthumb.php
497 ms
timthumb.php
585 ms
sketchfab.png
579 ms
timthumb.php
590 ms
timthumb.php
594 ms
timthumb.php
598 ms
timthumb.php
681 ms
timthumb.php
684 ms
timthumb.php
692 ms
timthumb.php
696 ms
timthumb.php
699 ms
timthumb.php
777 ms
timthumb.php
782 ms
timthumb.php
784 ms
timthumb.php
793 ms
__utm.gif
13 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJ6bQl2xMC.woff
33 ms
HhyJU5sn9vOmLxNkIwRSjTVNWLEJN7Ml2xMC.woff
77 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e4.woff
41 ms
timthumb.php
705 ms
timthumb.php
709 ms
timthumb.php
751 ms
timthumb.php
756 ms
timthumb.php
888 ms
timthumb.php
706 ms
timthumb.php
707 ms
timthumb.php
712 ms
timthumb.php
789 ms
timthumb.php
792 ms
timthumb.php
707 ms
timthumb.php
711 ms
timthumb.php
902 ms
timthumb.php
694 ms
timthumb.php
695 ms
timthumb.php
701 ms
timthumb.php
618 ms
timthumb.php
694 ms
timthumb.php
691 ms
timthumb.php
693 ms
timthumb.php
700 ms
case.png
618 ms
gommette.png
690 ms
gommette_line.png
687 ms
zooo.be accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
Links do not have a discernible name
zooo.be 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
General
Impact
Issue
Detected JavaScript libraries
zooo.be 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
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Zooo.be 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 Zooo.be 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.
zooo.be
Open Graph description is not detected on the main page of Zooo. 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: