2.8 sec in total
515 ms
2.2 sec
75 ms
Click here to check amazing Cloud Izzi content for France. Otherwise, check out these important facts you probably never knew about cloud.izzi.pro
Visit cloud.izzi.proWe analyzed Cloud.izzi.pro page load time and found that the first response time was 515 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
cloud.izzi.pro performance score
name
value
score
weighting
Value9.9 s
0/100
10%
Value9.9 s
0/100
25%
Value10.4 s
8/100
10%
Value50 ms
100/100
30%
Value0.005
100/100
15%
Value10.3 s
25/100
10%
515 ms
206 ms
260 ms
257 ms
209 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that all of those requests were addressed to Cloud.izzi.pro and no external sources were called. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Cloud.izzi.pro.
Page size can be reduced by 1.2 MB (82%)
1.4 MB
253.6 kB
In fact, the total size of Cloud.izzi.pro main page is 1.4 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. 20% of websites need less resources to load. Javascripts take 1.3 MB which makes up the majority of the site volume.
Potential reduce by 10.3 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 10.3 kB or 83% of the original size.
Potential reduce by 1.1 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.1 MB or 83% of the original size.
Potential reduce by 105.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. Cloud.izzi.pro needs all CSS files to be minified and compressed as it can save up to 105.9 kB or 82% of the original size.
Number of requests can be reduced by 60 (86%)
70
10
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Cloud Izzi. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 20 to 1 for CSS and as a result speed up the page load time.
cloud.izzi.pro
515 ms
styles.css
206 ms
header.css
260 ms
mobile.css
257 ms
icons.css
209 ms
fonts.css
260 ms
apps.css
262 ms
fixes.css
284 ms
multiselect.css
285 ms
jquery-ui.css
415 ms
jquery-ui-fixes.css
362 ms
jquery-tipsy.css
360 ms
jquery.ocdialog.css
365 ms
share.css
370 ms
versions.css
392 ms
lucene.css
501 ms
style.css
481 ms
mediaelementplayer.css
559 ms
colorbox.css
503 ms
firstrunwizard.css
500 ms
slideshow.css
506 ms
oc.js
819 ms
jquery.min.js
814 ms
jquery-migrate.min.js
582 ms
jquery-ui.custom.js
1071 ms
underscore.js
674 ms
moment-with-locales.js
1037 ms
handlebars.js
898 ms
placeholders.js
766 ms
jquery-tipsy.js
846 ms
compatibility.js
890 ms
jquery.ocdialog.js
893 ms
oc-dialogs.js
925 ms
js.js
1045 ms
l10n.js
973 ms
octemplate.js
976 ms
eventsource.js
1003 ms
config.js
858 ms
search.js
865 ms
oc-requesttoken.js
876 ms
apps.js
872 ms
snap.js
886 ms
placeholder.js
882 ms
md5.js
869 ms
jquery.avatar.js
903 ms
avatar.js
822 ms
backgroundjobs.js
843 ms
share.js
1046 ms
share.js
878 ms
external.js
867 ms
versions.js
846 ms
checker.js
786 ms
viewer.js
790 ms
previewplugin.js
832 ms
viewer.js
833 ms
jquery.colorbox.js
832 ms
firstrunwizard.js
785 ms
jquery.mousewheel-3.1.1.js
786 ms
slideshow.js
742 ms
public.js
650 ms
jstz.js
606 ms
visitortimezone.js
593 ms
lostpassword.js
601 ms
breadcrumb.svg
85 ms
part.results.html
85 ms
logo.svg
87 ms
loading-dark.gif
90 ms
user.svg
102 ms
password.svg
171 ms
OpenSans-Regular.woff
179 ms
OpenSans-Bold.woff
183 ms
cloud.izzi.pro accessibility score
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.
cloud.izzi.pro best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
cloud.izzi.pro SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Page is blocked from indexing
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Cloud.izzi.pro 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 Cloud.izzi.pro 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.
cloud.izzi.pro
Open Graph description is not detected on the main page of Cloud Izzi. 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: