6.2 sec in total
353 ms
3.8 sec
2.1 sec
Click here to check amazing Disruptive content. Otherwise, check out these important facts you probably never knew about disruptive.live
Disruptive Live - Home for the best in tech content from Disruptive Live and our partners
Visit disruptive.liveWe analyzed Disruptive.live page load time and found that the first response time was 353 ms and then it took 5.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
disruptive.live performance score
name
value
score
weighting
Value1.8 s
88/100
10%
Value5.6 s
18/100
25%
Value33.1 s
0/100
10%
Value59,200 ms
0/100
30%
Value0.14
79/100
15%
Value71.0 s
0/100
10%
353 ms
161 ms
262 ms
187 ms
66 ms
Our browser made a total of 101 requests to load all elements on the main page. We found that 46% of them (46 requests) were addressed to the original Disruptive.live, 12% (12 requests) were made to App-3qnjlom738.marketingautomation.services and 7% (7 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (2.6 sec) belongs to the original domain Disruptive.live.
Page size can be reduced by 170.6 kB (18%)
934.4 kB
763.8 kB
In fact, the total size of Disruptive.live main page is 934.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 494.5 kB which makes up the majority of the site volume.
Potential reduce by 106.1 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 106.1 kB or 86% of the original size.
Potential reduce by 14.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. Disruptive images are well optimized though.
Potential reduce by 18.6 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. This website has mostly compressed JavaScripts.
Potential reduce by 31.3 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. Disruptive.live needs all CSS files to be minified and compressed as it can save up to 31.3 kB or 24% of the original size.
Number of requests can be reduced by 55 (60%)
91
36
The browser has sent 91 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Disruptive. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 47 to 1 for JavaScripts and from 10 to 1 for CSS and as a result speed up the page load time.
disruptive.live
353 ms
disruptive.live
161 ms
owl.carousel.min.css
262 ms
styles.css
187 ms
style.css
66 ms
theme.css
67 ms
all.css
304 ms
gsap.min.js
190 ms
modernizr.js
34 ms
ScrollTrigger.min.js
208 ms
embed.js
195 ms
videoask-elements.js
79 ms
js
179 ms
js
199 ms
101294736.js
388 ms
iubenda_cs.js
197 ms
jquery.min.js
439 ms
init.js
288 ms
player.js
181 ms
index.js
120 ms
index.js
384 ms
js.cookie.min.js
178 ms
header.js
159 ms
footer.js
181 ms
nav_main.js
183 ms
story-teaser.js
191 ms
blocks.js
207 ms
blog.js
193 ms
popper.min.js
184 ms
bootstrap.min.js
195 ms
api.js
165 ms
regenerator-runtime.min.js
217 ms
wp-polyfill.min.js
644 ms
index.js
702 ms
form.js
172 ms
v652eace1692a40cfa3763df669d7439c1639079717194
260 ms
Tec-Dat-White.png
58 ms
Pal-Alt-wHITE.png
502 ms
Cele-White.png
103 ms
Unisus-White.png
500 ms
Leno-white.png
172 ms
Ignition-White.png
216 ms
ibeeM-White.png
217 ms
Sisco-White.png
540 ms
Ava-st-White.png
541 ms
Google-White.png
538 ms
236891962_917784848818533_7005722071706177853_n-768x0-c-default.webp
536 ms
Linkedin.png
779 ms
Twitter-logo.png
569 ms
Facebook.png
569 ms
Youtube-logo-1.png
568 ms
3.png
779 ms
Disruptive-Logo-White-for-website-2-190x0-c-default.png
1155 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVc.ttf
723 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVc.ttf
691 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4uaVc.ttf
721 ms
c.js
57 ms
analytics.js
289 ms
691891912
278 ms
722573907
417 ms
725318437
543 ms
692202905
554 ms
725301840
515 ms
725322963
520 ms
core-en.js
328 ms
recaptcha__en.js
197 ms
pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf
466 ms
pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf
720 ms
pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf
2636 ms
pxiEyp8kv8JHgFVrJJfedw.ttf
723 ms
fa-brands-400.woff
205 ms
in.php
719 ms
player.js
404 ms
player.css
299 ms
collect
91 ms
657996
373 ms
S002TU42M07TTUw1N9U1SUxL1E0yNkvTTUtONklLTktMAooDAA
294 ms
1400477313-d8f4b8dde069fad6708aa9224908d7cbad31cb533b49f8a8946bd6122ef9372d-d
1026 ms
formbasics.css
221 ms
jquery-ui.min.css
513 ms
base.css
515 ms
datetimepicker.css
511 ms
jquery-1.7.2.min.js
546 ms
jquery.validate.min.js
544 ms
additional-methods.min.js
562 ms
jquery.form.js
562 ms
jquery-ui.min.js
585 ms
datetimepicker.js
544 ms
jquery.placeholder.js
584 ms
api.js
217 ms
1401024590-017f7ca4e9dc6ccef8637accc3c1350220e869f72b56d850821dfce2648d92f2-d
400 ms
1455154619-51306a88f9620fafd2156c6c35d8f138b1437459f9ce54297eaa3bf28e3d6660-d
1109 ms
1460193956-e05d3580472a0ac1316ddaabfa3267d58c289699d27e24d9b9966005df5f5bed-d
1157 ms
1460223820-03465a65219c66499f82daf4596a445e94b2dbf66844296ef5592c0ea539758e-d
1250 ms
nr-spa-1216.min.js
180 ms
689d5b4562
104 ms
689d5b4562
67 ms
689d5b4562
96 ms
689d5b4562
72 ms
689d5b4562
53 ms
689d5b4562
51 ms
disruptive.live 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
Links do not have a discernible name
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
disruptive.live 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
Browser errors were logged to the console
Page has valid source maps
disruptive.live SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Disruptive.live 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 Disruptive.live 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.
disruptive.live
Open Graph data is detected on the main page of Disruptive. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: