2.1 sec in total
311 ms
1.2 sec
512 ms
Visit zillin.io now to see the best up-to-date Zillin content and also check out these interesting facts you probably never knew about zillin.io
The most user-friendly online tool for creating image datasets. Secure your images, annotate them, collaborate with others.
Visit zillin.ioWe analyzed Zillin.io page load time and found that the first response time was 311 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
zillin.io performance score
name
value
score
weighting
Value2.5 s
67/100
10%
Value5.3 s
21/100
25%
Value2.9 s
95/100
10%
Value10 ms
100/100
30%
Value0.058
98/100
15%
Value3.4 s
93/100
10%
311 ms
99 ms
202 ms
33 ms
146 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 64% of them (32 requests) were addressed to the original Zillin.io, 18% (9 requests) were made to Fonts.gstatic.com and 8% (4 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (509 ms) belongs to the original domain Zillin.io.
Page size can be reduced by 49.8 kB (8%)
621.1 kB
571.3 kB
In fact, the total size of Zillin.io main page is 621.1 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. 40% of websites need less resources to load. Images take 517.2 kB which makes up the majority of the site volume.
Potential reduce by 22.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 5.7 kB, which is 19% 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 22.6 kB or 77% of the original size.
Potential reduce by 21.5 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. Zillin images are well optimized though.
Potential reduce by 184 B
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. This website has mostly compressed JavaScripts.
Potential reduce by 5.4 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. Zillin.io has all CSS files already compressed.
Number of requests can be reduced by 12 (33%)
36
24
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Zillin. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
zillin.io
311 ms
bootstrap.min.css
99 ms
zillin.css
202 ms
css
33 ms
all.css
146 ms
js.cookie.min.js
25 ms
jquery.min.js
28 ms
popper.min.js
36 ms
bootstrap.min.js
292 ms
overlay.js
320 ms
smooth-scroll.min.js
319 ms
cookiesNotification.js
309 ms
campaigns.js
309 ms
readmore.min.js
321 ms
responsiveslides.min.js
365 ms
splash_ico_1.png
182 ms
splash_ico_2.png
174 ms
splash_ico_3.png
172 ms
splash_ico_4.png
182 ms
bg_1.jpg
456 ms
bg_tran_0.gif
219 ms
bg_tran_1.gif
252 ms
bg_tran_2.gif
257 ms
bg_tran_3.gif
257 ms
bg_tran_4.gif
282 ms
features_datasets.png
297 ms
features_teamwork.png
326 ms
features_review.png
350 ms
features_analysis.png
335 ms
zillin-isometric-inspection.png
431 ms
zillin-isometric-robot.png
384 ms
zillin-isometric-medical.png
403 ms
zillin-isometric-agriculture.png
487 ms
zillin-isometric-autonomous.png
432 ms
zillin-isometric-handling.png
473 ms
logo_white_text.png
490 ms
logo.svg
509 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf
17 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf
32 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf
40 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf
40 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf
41 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58a-xw.ttf
41 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58a-xw.ttf
41 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf
38 ms
6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58a-xw.ttf
45 ms
fa-solid-900.woff
84 ms
fa-regular-400.woff
134 ms
fa-brands-400.woff
168 ms
8Dn3lPJK32WRcAAAAASUVORK5CYII=
1 ms
zillin.io accessibility score
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
Image elements do not have [alt] attributes
Links do not have a discernible name
<object> elements do not have alternate text
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
zillin.io 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
Page has valid source maps
zillin.io 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
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 Zillin.io 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 Zillin.io 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.
zillin.io
Open Graph description is not detected on the main page of Zillin. 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: