disruptive.asia

disruptive.asia is SSL secured

Free website and domain report on disruptive.asia

Last Updated: 30th March, 2021 Update Now
Overview

Snoop Summary for disruptive.asia

This is a free and comprehensive report about disruptive.asia. The domain disruptive.asia is currently hosted on a server located in Brussels, Brussels Capital in Belgium with the IP address 35.195.187.5, where EUR is the local currency and the local language is German. Disruptive.asia has the potential to be earning an estimated $4 USD per day from advertising revenue. If disruptive.asia was to be sold it would possibly be worth $2,760 USD (based on the daily revenue potential of the website over a 24 month period). Disruptive.asia receives an estimated 1,322 unique visitors every day - a large amount of traffic! This report was last updated 30th March, 2021.

About disruptive.asia

Site Preview: disruptive.asia disruptive.asia
Title: Home
Description: Disruptive.Asia home covers the current state of digital disruption in the Asia-Pacific telecommunications industry and what's driving it.
Keywords and Tags: blogs, wiki
Related Terms: disruption, disruptive, disruptive technology
Fav Icon:
Age: Over 8 years old
Domain Created: 6th February, 2016
Domain Updated: 5th May, 2020
Domain Expires: 6th February, 2021
Review

Snoop Score

2/5

Valuation

$2,760 USD
Note: All valuation figures are estimates.

Popularity

Modest
Note: Popularity is estimated.

Rank, Reach and Authority

Alexa Rank: 641,049
Alexa Reach:
SEMrush Rank (US):
SEMrush Authority Score:
Moz Domain Authority: 0
Moz Page Authority: 0

Organic vs Paid (Google Ads)

Traffic

Visitors

Daily Visitors: 1,322
Monthly Visitors: 40,238
Yearly Visitors: 482,530
Note: All visitors figures are estimates.

Visitors By Country

Revenue

Revenue

Daily Revenue: $4 USD
Monthly Revenue: $115 USD
Yearly Revenue: $1,375 USD
Note: All revenue figures are estimates.

Revenue By Country

SEO

Backlinks Analysis (SEMrush)

Top New Follow Links

Top Ranking Keywords (US)

Domain Analysis

Value Length
Domain: disruptive.asia 15
Domain Name: disruptive 10
Extension (TLD): asia 4
Expiry Check:

Page Speed Analysis

Average Load Time: 4.71 seconds
Load Time Comparison: Faster than 10% of sites

PageSpeed Insights

Avg. (All Categories) 92
Performance 95
Accessibility 94
Best Practices 87
SEO 82
Progressive Web App 100
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on desktop
95

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for disruptive.asia. This includes details about optimizing page load times which can result in a better user experience.

Metrics

First Contentful Paint — 0.9 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 1.2 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 0.9 s
The timing of the largest text or image that is painted.
Time to Interactive — 0.9 s
The time taken for the page to become fully interactive.
Total Blocking Time — 0 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

First CPU Idle — 0.9 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 30 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 0.9 s
The time taken for the primary content of the page to be rendered.
Estimated Input Latency — 10 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive disruptive.asia as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://disruptive.asia/
http/1.1
0
211.03899972513
278
0
301
text/html
https://disruptive.asia/
h2
211.71299973503
604.78799976408
24799
185474
200
text/html
Document
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/db2071e4f5053a6504c918bf1fc7e57f.css
h2
617.70899966359
1299.0649999119
68342
423406
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Open+Sans:300,400,400italic,600,700&display=swap
h2
618.80300007761
634.86999971792
1562
11299
200
text/css
Stylesheet
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
h2
620.87700003758
705.38699999452
31497
89496
200
application/javascript
Script
https://disruptive.asia/superpwa-manifest.json
h2
732.42900008336
881.20099995285
752
0
200
application/json
Other
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/plugins/newsletter-leads/libs/simplemodal/jquery.simplemodal.js?ver=5.7
h2
631.08599977568
704.75299982354
7299
22831
200
application/javascript
Script
https://stats.wp.com/e-202113.js
h2
712.17399975285
728.29699981958
3252
8972
200
application/javascript
Script
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
h2
731.73999972641
785.4679999873
3052
7890
200
application/javascript
Script
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
h2
732.09999967366
1323.8820000552
71890
249996
200
application/javascript
Script
https://ssl.google-analytics.com/ga.js
h2
732.27000003681
736.67899984866
17798
46274
200
text/javascript
Script
data
737.43099998683
737.48299991712
0
68
200
image/svg+xml
Image
data
738.62499976531
738.6819999665
0
68
200
image/svg+xml
Image
data
740.00199977309
740.05399970338
0
68
200
image/svg+xml
Image
data
741.34499998763
741.38699984178
0
66
200
image/svg+xml
Image
data
743.33800002933
743.37999988347
0
66
200
image/svg+xml
Image
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
h2
757.6969997026
760.75699971989
9695
9132
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
h2
758.42499965802
762.12299987674
9643
9080
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem6YaGs126MiZpBA-UFUK0Zdc1GAK6b.woff2
h2
779.79899989441
783.3920000121
10290
9728
200
font/woff2
Font
https://pixel.wp.com/g.gif?v=ext&j=1%3A9.5&blog=113632871&post=5&tz=8&srv=disruptive.asia&host=disruptive.asia&ref=&fcp=0&rand=0.17653495979609768
h2
825.01100003719
839.30799970403
186
50
200
image/gif
Image
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=1703715497&utmhn=disruptive.asia&utmcs=UTF-8&utmsr=800x600&utmvp=1350x940&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Home&utmhid=480047749&utmr=-&utmp=%2F&utmht=1617082730113&utmac=UA-84808524-1&utmcc=__utma%3D23618735.362183101.1617082730.1617082730.1617082730.1%3B%2B__utmz%3D23618735.1617082730.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=769014096&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
http/1.1
875.58599980548
893.20399984717
757
0
302
text/html
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2017/11/DA_logo_215x100.jpg
h2
885.62300009653
900.35300003365
5841
5515
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Poker-17067920.jpg
h2
885.83200005814
951.6459996812
28095
27768
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-166223501-326x245.jpg
h2
886.11300010234
1091.4219999686
10237
9910
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Poker-17067920-326x245.jpg
h2
886.55199995264
1092.3939999193
7500
7173
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Scientific-microscope-in-a-nan-392501915-80x60.jpg
h2
886.83299999684
1067.2289999202
1603
1277
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/Universe-80x60.png
h2
887.1269999072
951.00799994543
4232
3908
200
image/png
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Businessman-Executive-Leading-395948159-80x60.jpg
h2
887.44599977508
923.97999996319
2523
2198
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Frightened-Woman-Has-Problem-W-412823641-80x60.jpg
h2
888.29799974337
908.22999970987
1835
1510
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/2021-03-29T113425Z_1_LYNXMPEH2S0RW_RTROPTP_4_TECH-ROBOTS-BOSTON-DYNAMICS-STRETCH-80x60.jpg
h2
889.72599990666
907.86499995738
2141
1816
200
image/jpeg
Image
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-84808524-1&cid=362183101.1617082730&jid=769014096&_v=5.7.2&z=1703715497
h2
893.4959997423
897.22199970856
663
35
200
image/gif
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/themes/mh-magazine/fonts/fontawesome-webfont.woff2?v=4.7.0
h2
1333.2469998859
1361.1909998581
77488
77160
200
font/woff2
Font
https://secure.tank3pull.com/Track/Capture.aspx?retType=js&trk_uid=&trk_user=197660&trk_sw=800&trk_sh=600&trk_ref=&trk_tit=Home&trk_loc=https%3A%2F%2Fdisruptive.asia%2F&trk_agn=Netscape&trk_agv=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_14_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F84.0.4143.7%20Safari%2F537.36%20Chrome-Lighthouse.lfcd24.lflngen-US&trk_dom=disruptive.asia&trk_cookie=9ab97abb-173a-4bd2-a95a-270f15db4d05-c197660-sw800-sh600-ms1617082730660-r1086021
http/1.1
1418.0609998293
1613.4669999592
92
0
200
text/plain
Script
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Orlando-fl-usa-A-Row-337716463-80x60.jpg
h2
1450.193000026
1641.9540001079
2041
1715
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578-80x60.jpg
h2
1450.445999857
1664.8450000212
1448
1122
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Annoying-Mobile-Spam-Angry-Fu-267821452-80x60.jpg
h2
1450.6230000407
1655.6540001184
1401
1075
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Psychedelic-Fantasy-Beautiful-286788436-80x60.jpg
h2
1451.0109997354
1668.171999976
4368
4042
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-d-Rendering-Futuristic-Robot-383299067-80x60.jpg
h2
1451.2069998309
1480.2399999462
2148
1823
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Businessman-Holds-Man-Person-I-409961905-80x60.jpg
h2
1452.7829997241
1542.0590001158
1455
1130
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Man-Divides-The-Arrow-Blocks-I-385316522-80x60.jpg
h2
1453.0770001002
1479.679999873
1832
1507
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578.jpg
h2
1834.4970000908
1862.2979996726
54107
53780
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Scientific-microscope-in-a-nan-392501915.jpg
h2
1835.0689997897
1854.5059999451
19839
19512
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
639.186
7.693
743.833
31.94
775.794
62.098
839.34
7.989
856.476
21.462
880.344
26.472
911.786
7.649
1335.406
15.802
1351.246
49.778
1403.146
7.38
1414.109
51.107
1465.296
8.933
1490.615
46.376
1537.629
6.173
1702.262
67.005
1769.282
35.299
1835.464
16.928
1852.425
11.829
1866.066
7.141
1873.226
9.7
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Eliminate render-blocking resources — Potential savings of 0 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Disruptive.asia should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
31497
80
Properly size images
Images can slow down the page's load time. Disruptive.asia should consider serving more appropriate-sized images.
Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Disruptive.asia should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Disruptive.asia should consider minifying CSS files.
Minify JavaScript — Potential savings of 4 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Disruptive.asia should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/plugins/newsletter-leads/libs/simplemodal/jquery.simplemodal.js?ver=5.7
7299
4174
Remove unused CSS — Potential savings of 64 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Disruptive.asia should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/db2071e4f5053a6504c918bf1fc7e57f.css
68342
65862
Remove unused JavaScript — Potential savings of 49 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
71890
50558
Efficiently encode images — Potential savings of 7 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578.jpg
53780
7559
Serve images in next-gen formats — Potential savings of 41 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578.jpg
53780
27382
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Poker-17067920.jpg
27768
14124
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 390 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://disruptive.asia/
394.072
Avoid multiple page redirects — Potential savings of 190 ms
Redirects can cause additional delays before the page can begin loading. Disruptive.asia should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://disruptive.asia/
190
https://disruptive.asia/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Disruptive.asia should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://disruptive.asia/
167
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
58
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 480 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/themes/mh-magazine/fonts/fontawesome-webfont.woff2?v=4.7.0
77488
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
71890
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/db2071e4f5053a6504c918bf1fc7e57f.css
68342
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578.jpg
54107
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
31497
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Poker-17067920.jpg
28095
https://disruptive.asia/
24799
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Scientific-microscope-in-a-nan-392501915.jpg
19839
https://ssl.google-analytics.com/ga.js
17798
https://fonts.gstatic.com/s/opensans/v18/mem6YaGs126MiZpBA-UFUK0Zdc1GAK6b.woff2
10290
Uses efficient cache policy on static assets — 2 resources found
Disruptive.asia can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://secure.tank3pull.com/Track/Capture.aspx?retType=js&trk_uid=&trk_user=197660&trk_sw=800&trk_sh=600&trk_ref=&trk_tit=Home&trk_loc=https%3A%2F%2Fdisruptive.asia%2F&trk_agn=Netscape&trk_agv=Mozilla%2F5.0%20(Macintosh%3B%20Intel%20Mac%20OS%20X%2010_14_6)%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F84.0.4143.7%20Safari%2F537.36%20Chrome-Lighthouse.lfcd24.lflngen-US&trk_dom=disruptive.asia&trk_cookie=9ab97abb-173a-4bd2-a95a-270f15db4d05-c197660-sw800-sh600-ms1617082730660-r1086021
0
92
https://ssl.google-analytics.com/ga.js
7200000
17798
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Disruptive.asia should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.2 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://disruptive.asia/
329.323
9.092
3.499
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
167.423
115.51
1.968
Unattributable
68.44
2.685
0.242
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
51.104
25.106
5.134
Minimizes main-thread work — 0.7 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Script Evaluation
200.359
Style & Layout
182.928
Other
138.571
Rendering
108.134
Parse HTML & CSS
27.822
Script Parsing & Compilation
16.118
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 37 requests • 480 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
37
491981
Image
20
153495
Script
7
134880
Font
4
107116
Stylesheet
2
69904
Document
1
24799
Other
3
1787
Media
0
0
Third-party
34
466152
Minimize third-party usage — Third-party code blocked the main thread for 0 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
412214
0
31190
0
18555
0
3438
0
663
0
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.20723294350879
0.0097856687893926
0.0097856687893926
0.0067501634671417
0.0067501634671417
Uses passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

Cumulative Layout Shift — 0.245
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Diagnostics

Avoid an excessive DOM size — 932 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
932
Maximum DOM Depth
i
17
Maximum Child Elements
20
94

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of disruptive.asia. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
Links have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Disruptive.asia may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-hidden="true"]` elements contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
Ok

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
87

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that disruptive.asia should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Serves images with appropriate resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
FlexSlider
WordPress
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://disruptive.asia/
Allowed

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
TypeError: Failed to update a ServiceWorker for scope ('https://disruptive.asia/') with script ('https://disruptive.asia/superpwa-sw.js'): An unknown error occurred when fetching the script.
82

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for disruptive.asia. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of disruptive.asia on mobile screens.
Document uses legible font sizes
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Tap targets are sized appropriately
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
100

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of disruptive.asia. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of disruptive.asia on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Avg. (All Categories) 86
Performance 78
Accessibility 92
Best Practices 80
SEO 81
Progressive Web App 100
0–49 (Fail) 50–89 (Average) 90–100 (Pass)
Simulate loading on mobile
78

Performance

Indicates how well the page is performing and highlights opportunities where performance may be improved for disruptive.asia. This includes details about optimizing page load times which can result in a better user experience.

Metrics

Total Blocking Time — 280 ms
The total blocking time is the sum of all time periods between First Contentful Paint and Time to Interactive (when task length exceeded 50ms).

Other

Estimated Input Latency — 50 ms
The time taken for the page to respond to user input (during the busiest 5 second window of page load). Users are likely to perceive disruptive.asia as laggy when the latency is higher than 0.05 seconds.
Network Requests
Below is a list of network requests that were made during page load.
URL Protocol Start Time (Ms) End Time (Ms) Transfer Size (Bytes) Resource Size (Bytes) Status Code MIME Type Resource Type
http://disruptive.asia/
http/1.1
0
95.674999989569
251
0
301
text/html
https://disruptive.asia/
h2
96.268000081182
237.62900009751
24857
185543
200
text/html
Document
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/db2071e4f5053a6504c918bf1fc7e57f.css
h2
255.65700000152
305.97000010312
68341
423406
200
text/css
Stylesheet
https://fonts.googleapis.com/css?family=Open+Sans:300,400,400italic,600,700&display=swap
h2
256.45199976861
330.8979999274
1562
11299
200
text/css
Stylesheet
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
h2
259.32199973613
292.94200008735
31497
89496
200
application/javascript
Script
https://disruptive.asia/superpwa-manifest.json
h2
324.44200012833
420.74199998751
752
0
200
application/json
Other
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/plugins/newsletter-leads/libs/simplemodal/jquery.simplemodal.js?ver=5.7
h2
270.36199998111
289.1069999896
7299
22831
200
application/javascript
Script
https://stats.wp.com/e-202113.js
h2
323.12799990177
338.2129999809
3252
8972
200
application/javascript
Script
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
h2
323.58400011435
341.186999809
3052
7890
200
application/javascript
Script
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
h2
323.85599985719
352.02999971807
71889
249996
200
application/javascript
Script
https://ssl.google-analytics.com/ga.js
h2
324.13200009614
331.57499972731
17798
46274
200
text/javascript
Script
data
330.40999993682
330.46199986711
0
68
200
image/svg+xml
Image
data
331.78399968892
331.83000003919
0
68
200
image/svg+xml
Image
data
333.33399984986
333.43000011519
0
68
200
image/svg+xml
Image
data
334.87399993464
334.94099974632
0
66
200
image/svg+xml
Image
data
338.2270000875
338.30099971965
0
66
200
image/svg+xml
Image
https://pixel.wp.com/g.gif?v=ext&j=1%3A9.5&blog=113632871&post=5&tz=8&srv=disruptive.asia&host=disruptive.asia&ref=&fcp=0&rand=0.25138372014299404
h2
427.13199974969
441.15399988368
186
50
200
image/gif
Image
https://fonts.gstatic.com/s/opensans/v18/mem8YaGs126MiZpBA-UFVZ0bf8pkAg.woff2
h2
433.56100004166
436.51499971747
9695
9132
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UN7rgOUuhpKKSTjw.woff2
h2
435.37999968976
438.63500002772
9643
9080
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem6YaGs126MiZpBA-UFUK0Zdc1GAK6b.woff2
h2
440.0899996981
443.01499985158
10291
9728
200
font/woff2
Font
https://secure.tank3pull.com/Track/Capture.aspx?retType=js&trk_uid=&trk_user=197660&trk_sw=360&trk_sh=640&trk_ref=&trk_tit=Home&trk_loc=https%3A%2F%2Fdisruptive.asia%2F&trk_agn=Netscape&trk_agv=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F84.0.4143.7%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse.lfcd24.lflngen-US&trk_dom=disruptive.asia&trk_cookie=f436562f-f06d-4854-b9b2-9d5c20079cce-c197660-sw360-sh640-ms1617082756921-r3927412
http/1.1
489.44599973038
793.47099969164
92
0
200
text/plain
Script
https://ssl.google-analytics.com/r/__utm.gif?utmwv=5.7.2&utms=1&utmn=47516399&utmhn=disruptive.asia&utmcs=UTF-8&utmsr=360x640&utmvp=360x640&utmsc=24-bit&utmul=en-us&utmje=0&utmfl=-&utmdt=Home&utmhid=1466536471&utmr=-&utmp=%2F&utmht=1617082756961&utmac=UA-84808524-1&utmcc=__utma%3D23618735.872227669.1617082757.1617082757.1617082757.1%3B%2B__utmz%3D23618735.1617082757.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B&utmjid=571847324&utmredir=1&utmu=qAAAAAAAAAAAAAAAAAAAAAAE~
http/1.1
533.63199997693
598.92100002617
755
0
302
text/html
https://stats.g.doubleclick.net/r/collect?v=1&aip=1&t=dc&_r=3&tid=UA-84808524-1&cid=872227669.1617082757&jid=571847324&_v=5.7.2&z=47516399
h2
599.37800001353
603.19299995899
663
35
200
image/gif
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2017/11/DA_logo_215x100.jpg
h2
602.84399986267
616.41700007021
5841
5515
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-166223501-326x245.jpg
h2
604.39600003883
619.83399977908
10236
9910
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Orlando-fl-usa-A-Row-337716463-326x245.jpg
h2
604.55199982971
868.86199982837
17189
16861
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/themes/mh-magazine/fonts/fontawesome-webfont.woff2?v=4.7.0
h2
648.25499989092
664.77499995381
77488
77160
200
font/woff2
Font
https://fonts.gstatic.com/s/opensans/v18/mem5YaGs126MiZpBA-UNirkOUuhpKKSTjw.woff2
h2
669.35599967837
672.482999973
9741
9180
200
font/woff2
Font
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578-326x245.jpg
h2
742.12699988857
925.49999989569
10236
9909
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/2021-03-29T113425Z_1_LYNXMPEH2S0RW_RTROPTP_4_TECH-ROBOTS-BOSTON-DYNAMICS-STRETCH-326x245.jpg
h2
742.39799985662
759.24400007352
16144
15817
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Annoying-Mobile-Spam-Angry-Fu-267821452-326x245.jpg
h2
742.60400002822
758.71399976313
5561
5235
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/2021-03-26T165035Z_1_LYNXMPEH2P1JP_RTROPTP_4_USA-TECH-CONGRESS-326x245.jpg
h2
743.46099980175
936.04800011963
7377
7050
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578.jpg
h2
1127.8829998337
1156.0479998589
54107
53780
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Poker-17067920.jpg
h2
1128.1320000999
1149.7220001183
28095
27768
200
image/jpeg
Image
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Scientific-microscope-in-a-nan-392501915.jpg
h2
1128.9069997147
1143.2559997775
19839
19512
200
image/jpeg
Image
Network Round Trip Times — 0 ms
High Network RTT (Round Trip Times) can have a large impact on performance. Providing servers geographically closer to the user could improve performance.
Server Backend Latencies — 0 ms
High server latencies indicate the server is overloaded or has a poor backend performance.
Tasks
Below is a list of the top-level main thread tasks that executed during page load.
Start Time (Ms) End Time (Ms)
270.388
10.263
329.121
39.229
368.376
61.474
430.986
6.801
456.87
37.341
495.297
35.697
534.694
28.031
570.766
19.474
605.849
21.94
632.802
113.571
746.406
14.981
772.793
6.711
779.641
25.099
806.393
10.607
899.944
9.769
966.667
94.971
1061.688
48.633
1118.706
20.404
1139.199
15.108
1157.328
13.339
1170.704
13.755
Diagnostics
Below is a collection of useful page vitals.
View Data
Metrics
Below is a collection of metrics.
View Data

Opportunities

Defer offscreen images
Time to Interactive can be slowed down by resources on the page. Disruptive.asia should consider lazy-loading offscreen and hidden images.
Minify CSS
Cascading Style Sheets (CSS) files can contribute to network payload sizes. Disruptive.asia should consider minifying CSS files.
Minify JavaScript — Potential savings of 4 KiB
JavaScript (JS) files can contribute to network payload sizes and increase script parse times. Disruptive.asia should consider minifying JS files.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/plugins/newsletter-leads/libs/simplemodal/jquery.simplemodal.js?ver=5.7
7299
4174
Efficiently encode images — Potential savings of 7 KiB
Unoptimized images can consume more cellular data than what is necessary.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578.jpg
53780
7559
Enable text compression
Text-based resources should be served with compression, such as gzip, deflate or brotli.
Preconnect to required origins
Resource hints, such as 'preconnect' or 'dns-prefetch', may assist in establishing early connections to important third-party origins.
Initial server response time was short — Root document took 140 ms
It is advised to keep the server response time short for the main document, because all other requests depend on it.
URL Time Spent (Ms)
https://disruptive.asia/
142.357
Avoid multiple page redirects — Potential savings of 630 ms
Redirects can cause additional delays before the page can begin loading. Disruptive.asia should avoid multiple or unnecessary page redirects.
URL Time Spent (Ms)
http://disruptive.asia/
630
https://disruptive.asia/
0
Preload key requests
Key requests can be preloaded by using '<link rel=preload>'. Disruptive.asia should consider using '<link rel=preload>' to prioritize fetching resources that are currently requested later in page load.
Use video formats for animated content
Large GIFs are inefficient for delivering animated content. It is recommended to use MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF.
Remove duplicate modules in JavaScript bundles
Ensure that no duplicate JavaScript modules from bundles exist to reduce bytes consumed by network activity.
Avoid serving legacy JavaScript to modern browsers — Potential savings of 0 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. For bundled JavaScript it is recommended to adopt a modern script deployment strategy using module/nomodule feature detection. This will reduce the amount of code shipped to modern browsers.
URL Potential Savings (Bytes)
https://disruptive.asia/
167
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
58
Preload Largest Contentful Paint image
It is recommended to preload images used by LCP elements, to improve LCP time.

Diagnostics

Avoids enormous network payloads — Total size was 511 KiB
Large network payloads can cost users money and are linked to long load times.
URL Transfer Size (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/themes/mh-magazine/fonts/fontawesome-webfont.woff2?v=4.7.0
77488
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
71889
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/db2071e4f5053a6504c918bf1fc7e57f.css
68341
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578.jpg
54107
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
31497
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Poker-17067920.jpg
28095
https://disruptive.asia/
24857
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Scientific-microscope-in-a-nan-392501915.jpg
19839
https://ssl.google-analytics.com/ga.js
17798
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Orlando-fl-usa-A-Row-337716463-326x245.jpg
17189
Uses efficient cache policy on static assets — 2 resources found
Disruptive.asia can speed up repeat visits by increasing the cache lifetime, which is essentially how long before a cached copy expires.
URL Cache TTL (Ms) Transfer Size (Bytes)
https://secure.tank3pull.com/Track/Capture.aspx?retType=js&trk_uid=&trk_user=197660&trk_sw=360&trk_sh=640&trk_ref=&trk_tit=Home&trk_loc=https%3A%2F%2Fdisruptive.asia%2F&trk_agn=Netscape&trk_agv=Mozilla%2F5.0%20(Linux%3B%20Android%207.0%3B%20Moto%20G%20(4))%20AppleWebKit%2F537.36%20(KHTML%2C%20like%20Gecko)%20Chrome%2F84.0.4143.7%20Mobile%20Safari%2F537.36%20Chrome-Lighthouse.lfcd24.lflngen-US&trk_dom=disruptive.asia&trk_cookie=f436562f-f06d-4854-b9b2-9d5c20079cce-c197660-sw360-sh640-ms1617082756921-r3927412
0
92
https://ssl.google-analytics.com/ga.js
7200000
17798
Avoid chaining critical requests — 2 chains found
Below is a list of Critical Request Chains, which shows which resources are loaded with a high priority. Disruptive.asia should consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
User Timing marks and measures
Make use of the User Timing API to measure an app's real-world performance during key user experiences.
JavaScript execution time — 0.9 s
JavaScript (JS) execution time can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
URL Total CPU Time (Ms) Script Evaluation (Ms) Script Parse (Ms)
https://disruptive.asia/
1413.552
40.452
14.784
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
1125.32
564.448
6.484
Unattributable
281.16
15.124
0.824
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
161.164
103.428
23.856
https://ssl.google-analytics.com/ga.js
113.16
104.384
4.352
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
75.036
60.892
4.62
All text remains visible during webfont loads
Make use of the font-display CSS feature, which will ensure text is user-visible while webfonts are loading.
Keep request counts low and transfer sizes small — 30 requests • 511 KiB
It is advised to add a budgets.json file in order to set budgets for the quantity and size of page resources.
Resource Type Requests Transfer Size (Bytes)
Total
30
523729
Image
12
175474
Script
7
134879
Font
5
116858
Stylesheet
2
69903
Document
1
24857
Other
3
1758
Media
0
0
Third-party
27
497869
Lazy load third-party resources with facades
Consider replacing third-party embeds with a facade until they are required (use lazy loading).
Largest Contentful Paint element — 1 element found
The element which was identified as the Largest Contentful Paint.
Element
Avoid large layout shifts — 5 elements found
Below is a list of all DOM elements that contribute to the CLS of the page.
Element CLS Contribution
0.61157161437796
0.282963314074
0.072127903587491
0.06226425865245
0.022249624388059
Avoids `document.write()`
Avoid or limit the use of external scripts that are dynamically injected via 'document.write()' as users on slow connections will be delayed by tens of seconds.
Avoid long main-thread tasks — 10 long tasks found
Below is a list of the longest tasks on the main thread, which is useful when identifying the worst input delay contributors.
URL Start Time (Ms) Duration (Ms)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
5536
227
https://disruptive.asia/
651
195
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/plugins/wp-rocket/assets/js/lazyload/16.1/lazyload.min.js
5763
190
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
5340
143
https://disruptive.asia/
1320
123
https://disruptive.asia/
3090
88
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
3540
78
https://disruptive.asia/
1443
75
https://ssl.google-analytics.com/ga.js
4548
56
https://disruptive.asia/
1518
50
Avoid non-composited animations — 1 animated element found
It is recommended to avoid non-composited animations which are often janky and increase CLS.
Element Name
Image elements have explicit `width` and `height`
Reduce layout shifts and improve CLS by setting explicit width and height properties on image elements.

Budgets

Performance budget
It is advised to keep the quantity and size of all network requests under the targets set by the provided performance budget.
Timing budget
It is advised to set a timing budget to monitor the performance of your site.

Metrics

First Contentful Paint — 2.7 s
The time taken for the first image or text on the page to be rendered.
Speed Index — 3.8 s
The time taken for the page contents to be visibly populated.
Largest Contentful Paint — 2.9 s
The timing of the largest text or image that is painted.
Time to Interactive — 5.6 s
The time taken for the page to become fully interactive.

Other

First CPU Idle — 5.3 s
The time taken for the page's main thread to be quiet enough to handle input.
Max Potential First Input Delay — 230 ms
Users could experience a delay when interacting with the page.
First Meaningful Paint — 2.7 s
The time taken for the primary content of the page to be rendered.
First Contentful Paint (3G) — 5490 ms
The time taken for the first image or text on the page to be rendered while on a 3G network.

Opportunities

Eliminate render-blocking resources — Potential savings of 230 ms
Resources, such as JavaScript and style sheets, can block the first paint of the page. Disruptive.asia should consider delivering critical JavaScript/style sheets (JS/CSS) inline and deferring all non-critical JS/CSS.
URL Transfer Size (Bytes) Potential Savings (Ms)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-includes/js/jquery/jquery.min.js?ver=3.5.1
31497
150
Properly size images — Potential savings of 24 KiB
Images can slow down the page's load time. Disruptive.asia should consider serving more appropriate-sized images.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/2021-03-29T113425Z_1_LYNXMPEH2S0RW_RTROPTP_4_TECH-ROBOTS-BOSTON-DYNAMICS-STRETCH-326x245.jpg
15817
9267
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-166223501-326x245.jpg
9910
5806
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578-326x245.jpg
9909
5806
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/2021-03-26T165035Z_1_LYNXMPEH2P1JP_RTROPTP_4_USA-TECH-CONGRESS-326x245.jpg
7050
4131
Remove unused CSS — Potential savings of 64 KiB
Dead and/or unused rules in Style Sheets (CSS) can contribute to network payload sizes. Disruptive.asia should consider removing dead rules from style sheets and deferring the loading of CSS not used for above-the-fold content.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/db2071e4f5053a6504c918bf1fc7e57f.css
68341
65350
Remove unused JavaScript — Potential savings of 49 KiB
It is advised to remove unused JavaScript in order to reduce bytes consumed by network activity.
URL Transfer Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/cache/min/1/b04b971c66f99fe4aa958be903683eb7.js
71889
50467
Serve images in next-gen formats — Potential savings of 41 KiB
Image formats like PNG and JPEG have poor compression when compared to other next-gen formats, such as JPEG 200, JPEG XR and WebP.
URL Resource Size (Bytes) Potential Savings (Bytes)
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Dark-Blue-Ocean-Surface-Seen-F-392520578.jpg
53780
27382
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2021/03/bigstock-Poker-17067920.jpg
27768
14124

Diagnostics

Avoid an excessive DOM size — 932 elements
A large DOM (Document Object Model) will increase memory usage, cause longer system calculations as well as costly layout reflows.
Statistic Element Value
Total DOM Elements
932
Maximum DOM Depth
i
17
Maximum Child Elements
20
Minimize main-thread work — 3.2 s
Main-thread work timing can be lowered by reducing the time required for parsing, compiling and executing JS. Delivering smaller JS payloads may help with this.
Category Time Spent (Ms)
Style & Layout
1043.788
Script Evaluation
902.216
Other
586.724
Rendering
444.884
Parse HTML & CSS
147.22
Script Parsing & Compilation
63.684
Garbage Collection
5.456

Metrics

Cumulative Layout Shift — 1.104
Cumulative Layout Shift is the measurement of visible elements collective movement within the viewport.
View Data

Diagnostics

Reduce the impact of third-party code — Third-party code blocked the main thread for 500 ms
It is advised to either limit, remove or delay the loading of redundant third-party code which may be significantly impacting load performance.
Third-Party Transfer Size (Bytes) Main-Thread Blocking Time (Ms)
434191
448.14
18553
50.928
40932
0
3438
0
663
0
Does not use passive listeners to improve scrolling performance
Improve the page's scroll performance by marking touch and wheel event listeners as 'passive'.
Source
92

Accessibility

Indicates how accessible the page is and highlights opportunities where the page can be made more accessible to users of disruptive.asia. This includes details about various page attributes that can be optimized.

Navigation

`[accesskey]` values are unique
Access keys assist users with focusing on different parts of the page. Each access key should be unique for proper navigation.
The page contains a heading, skip link, or landmark region
It is advised to provide ways to bypass repetitive content, allowing users to navigate the page efficiently.
`[id]` attributes on active, focusable elements are unique
Ensure all focusable elements have a unique id value to allow them to be visible to users of assistive technologies, like a screen reader.
No element has a `[tabindex]` value greater than 0
Although technically valid, a tabindex value greater than 0 often creates frustrating experiences for users who rely on assistive technologies.

ARIA

`[aria-*]` attributes match their roles
Avoid mismatching 'aria-*' attributes and their 'role' value, as it invalidates the attribute.
`button`, `link`, and `menuitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-hidden="true"]` is not present on the document `<body>`
If aria-hidden=true is set on the document body, assistive technologies, like a screen reader will work inconsistently.
ARIA input fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when an input field does not have an accessible name specified.
ARIA `meter` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `progressbar` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[role]`s have all required `[aria-*]` attributes
Some ARIA roles have required 'aria-*' attributes, which provide essential information about state and functionality.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
Some ARIA parent roles cannot perform their intended functions if specific child roles are not used.
`[role]`s are contained by their required parent element
Some ARIA child roles cannot perform their intended functions if specific parent roles are not used.
`[role]` values are valid
All ARIA roles require valid values to perform their intended functions.
ARIA toggle fields have accessible names
Generic names are announced to users of assistive technologies, like a screen reader, when a toggle field does not have an accessible name specified.
ARIA `tooltip` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
ARIA `treeitem` elements have accessible names
Without accessible names on elements, screen readers will default to announcing a generic name, which means your content will be less accessible to users who rely on screen readers.
`[aria-*]` attributes have valid values
ARIA attributes cannot be interpreted with invalid values when used by screen readers and other assistive technologies.
`[aria-*]` attributes are valid and not misspelled
ARIA attributes cannot be interpreted with invalid names when used by screen readers and other assistive technologies.
ARIA IDs are unique
Ensure all ARIA ID values are unique to prevent elements from being overlooked by assistive technologies, like a screen reader.

Names and labels

Buttons have an accessible name
Buttons become unusable as they are announced simply as "button" when the button does not have an accessible name, when used by screen readers and other assistive technologies.
Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
No form fields have multiple labels
Having multiple labels for form fields can be confusing to assistive technologies, like a screen reader.
`<frame>` or `<iframe>` elements have a title
Screen reader users and other assistive technology users rely on frame titles to describe the contents of frames.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
`<input type="image">` elements have `[alt]` text
Input buttons with alternative text assist screen readers and other assistive technology users to understand its purpose.
Form elements have associated labels
Screen readers and other assistive technologies rely on labels to properly announce form controls.
`<object>` elements have `[alt]` text
It is advised that alt text is used on '<object>' elements in order to provide meaning to screen reader and other assistive technology users, as these technologies are unable to translate non-text content.

Tables and lists

`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Screen readers and other assistive technologies may produce poor and inaccurate output when definition lists are not properly marked up.
Definition list items are wrapped in `<dl>` elements
In order for screen readers and other assistive technologies to properly announce definition list items ('<dt>' and '<dd>'), they must be wrapped in parent a '<dl>' element.
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Use proper list structure to aid screen readers and other assistive technologies.
List items (`<li>`) are contained within `<ul>` or `<ol>` parent elements
In order for screen readers to announce list items, ensure that list items ('<li>') are contained within parent '<ul>' or '<ol>' tags.
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that '<td>' cells using the headers attribute only refer to other cells in the same table, to improve screen reader user experience.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
Screen readers and other assistive technologies have features to make navigating tables easier. Ensure that table headers refer to some set of cells, to improve screen reader user experience.

Internationalization and localization

`<html>` element has a `[lang]` attribute
It is advised to provide a lang attribute so that screen readers and other assistive technologies are guaranteed to announce the page's text correctly. When not provided, the user's default language setting will be used which may cause inaccuracies.
`<html>` element has a valid value for its `[lang]` attribute
Specify a valid BCP 47 language in order to help screen readers and other assistive technologies announce text properly.
`[lang]` attributes have a valid value
Specify a valid BCP 47 language on elements in order to help screen readers and other assistive technologies announce text properly.

Best practices

The document does not use `<meta http-equiv="refresh">`
Pages that refresh automatically cause a poor user experience as focus is directed back to the top of the page unexpectedly.
`[user-scalable="no"]` is not used in the `<meta name="viewport">` element and the `[maximum-scale]` attribute is not less than 5.
For users with low vision who rely on screen magnification, ensure that zooming is not disabled.

Audio and video

`<video>` elements contain a `<track>` element with `[kind="captions"]`
Disruptive.asia may provide assistance to deaf or hearing-impaired users with captions on videos.

ARIA

`[aria-hidden="true"]` elements contain focusable descendents
Interactive elements within an aria-hidden=true element are unavailable to users of assistive technologies, like a screen reader.
Failing Elements

Contrast

Background and foreground colors do not have a sufficient contrast ratio.
Many (if not most) users find low-contrast text difficult or impossible to read.
Failing Elements
Ok

Navigation

Heading elements are not in a sequentially-descending order
Properly order all headers and do not skip heading levels to better the navigation and readability for users of assistive technologies, like a screen reader.
Failing Elements

Names and labels

Links do not have a discernible name
In order to improve the navigation for screen reader and other assistive technology users, use link text that is unique, focusable and discernible.

Manual Checks

The page has a logical tab order
The visual layout should be logical in its tab order and users cannot focus elements that are offscreen.
Interactive controls are keyboard focusable
Ensure that custom interactive controls are keyboard focusable and that a focus indicator is displayed.
Interactive elements indicate their purpose and state
Ensure that interactive elements (such as links and buttons) are distinguishable from non-interactive elements and that they indicate their state.
The user's focus is directed to new content added to the page
When new content (such as a dialogue) is added to the page, the user's focus should be directed to it.
User focus is not accidentally trapped in a region
Avoid focus being accidentally trapped when a user tabs in and out of controls or regions on page.
Custom controls have associated labels
Ensure that custom interactive controls have associated labels, which are provided by aria-label and aria-labelledby attributes.
Custom controls have ARIA roles
Ensure that all custom interactive controls have appropriate ARIA roles.
Visual order on the page follows DOM order
Ensure that the DOM order matches with the page's visual order, in order to improve navigation for screen readers and other assistive technologies.
Offscreen content is hidden from assistive technology
Ensure that offscreen content is hidden through the use of "display:none" styling or the aria-hidden attribute.
HTML5 landmark elements are used to improve navigation
Elements such as <main> and <nav> are recommended as they are used by screen readers and other assistive technologies to improve keyboard navigation.
80

Best Practices

Indicates the recommended, best practices currently in place on the page and highlights the best practices that disruptive.asia should incorporate. This includes practices such as protecting pages with HTTPS.

Audits

Links to cross-origin destinations are safe
Improve performance and prevent security vulnerabilities by adding rel="noopener" and rel="noreferrer" to external links.
Avoids requesting the geolocation permission on page load
When requesting a user's location, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids requesting the notification permission on page load
When requesting permission to send notifications, provide context or consider tying the request to a user action to avoid confusion and mistrust from users.
Avoids front-end JavaScript libraries with known security vulnerabilities
Ensure that the use of third-party scripts is minimal and that only trusted third-party scripts are used as some may contain known security vulnerabilities which may be exploited by attackers.

Audits

Allows users to paste into password fields
Ensure that password inputs may be pasted into to aid in the user's ability to use password managers and improve security.
Displays images with correct aspect ratio
Ensure that image display dimensions match their natural aspect ratio.
Fonts with `font-display: optional` are preloaded
It is recommended that optional fonts are preloaded.

Audits

Page has the HTML doctype
Ensure a doctype is specified to prevent the browser from switching to quirks-mode.
Properly defines charset
It is advised to declare a character encoding, optionally via a <meta> tag in the first 1024 bytes of the HTML or in the Content-Type HTTP response header.

Audits

Avoids `unload` event listeners
The 'unload' event does not fire reliably, causing issues with browser optimizations such as the Back-Forward Cache. It is recommended that 'pagehide' or 'visibilitychange' events are used instead.
Avoids Application Cache
Application cache is deprecated and is no longer recommended.
Detected JavaScript libraries
Below is a list of all front-end JavaScript libraries that were detected on the page.
Name Version
jQuery
3.5.1
FlexSlider
WordPress
Avoids deprecated APIs
Avoid deprecated APIs which will eventually be removed the browser.
Page has valid source maps
Consider deploying source maps for added benefits such as the ability to debug while in production.
No issues in the `Issues` panel in Chrome Devtools
There may be unresolved issues logged to Chrome Devtools.

Audits

Does not use HTTPS — 1 insecure request found
Ensure that all pages are protected with HTTPS (including those that do not handle sensitive data) as HTTPS prevents tampering and passive listening on communications between the app and its users. Additionally, HTTPS is a prerequisite for HTTP/2 and many new web platform APIs.
Insecure URL Request Resolution
http://disruptive.asia/
Allowed

Audits

Serves images with low resolution
For maximum image clarity, ensure images have natural dimensions and are proportional to the display size and pixel ratio.
URL Displayed size Actual size Expected size
https://499ioen9wh92k2blb3elevg9-wpengine.netdna-ssl.com/wp-content/uploads/2017/11/DA_logo_215x100.jpg
215 x 100
215 x 100
430 x 200

Audits

Browser errors were logged to the console
Below is a list of all errors logged to the console, which indicate unresolved problems on the site.
Source Description
TypeError: Failed to update a ServiceWorker for scope ('https://disruptive.asia/') with script ('https://disruptive.asia/superpwa-sw.js'): An unknown error occurred when fetching the script.
81

SEO

Indicates how well the page is optimized for ranking in search engines and highlights Search Engine Optimization (SEO) opportunities for disruptive.asia. This includes optimizations such as providing meta data.

Mobile Friendly

Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of disruptive.asia on mobile screens.
Document uses legible font sizes — 95.8% legible text
Font sizes of 12px or less are too small to most mobile users without user gestures and further action. Aim for more than 60% of page text to use font sizes greater than 12px.
Source Selector % of Page Text Font Size
html, body, div, span, applet, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, big, cite, code, del, dfn, em, img, ins, kbd, q, s, samp, small, strike, strong, sub, sup, tt, var, b, u, i, center, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, article, aside, canvas, details, embed, figure, figcaption, footer, header, hgroup, menu, nav, output, ruby, section, summary, time, mark, audio, video
3.50%
11px
0.71%
< 12px
95.80%
≥ 12px

Content Best Practices

Document has a `<title>` element
Search engines, screen reader users and other assistive technology users rely on the title to provide an overview of the page and to help determine if the page is relevant to their search.
Document has a meta description
Meta descriptions may be used by search engines when displaying a link to the page and should concisely summarize the page's content.
Links have descriptive text
Make use of descriptive link text to assist search engines in understanding the content.
Image elements have `[alt]` attributes
Provide short and descriptive alternative text where possible on informative elements.
Document has a valid `hreflang`
Search engines can be instructed to list specific versions of a page for a given language or region through the use of hreflang links.
Document has a valid `rel=canonical`
Search engines can be suggested which URL should be shown in search results through the use of canonical links.
Document avoids plugins
The content of plugins cannot be indexed by search engines and many devices either restrict or do not support them.

Crawling and Indexing

Page has successful HTTP status code
Avoid pages with unsuccessful HTTP status codes as they may not be indexed by search engines.
robots.txt is valid
Malformed robots.txt files prevent crawlers from understanding how a site wants to be crawled or indexed, which can be devastating to SEO.

Mobile Friendly

Tap targets are not sized appropriately — 65% appropriately sized tap targets
Interactive elements (such as buttons and links) should be appropriately spaced, sized and easy enough to select or tap with regard to their surrounding elements.
Tap Target Size Overlapping Target
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
0
6x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
77x15
71x15
77x15
77x15
77x15
0
6x15
0
6x15
320x26
77x15
77x15
77x15
77x15
77x15
77x15
77x15
320x31
320x31
320x31
77x15

Crawling and Indexing

Links are not crawlable
Ensure that the 'href' attribute of anchor elements links to the appropriate destination. This allows for more pages of the site to be discovered by search engines.
Page is blocked from indexing
Pages that cannot be crawled by search engines cannot be indexed or included in their search results. Ensure that search engines have permission to crawl all pages that should be indexed.
Blocking Directive Source

Manual Checks

Structured data is valid
Structured data can be validated through the use of the Structured Data Testing Tool and the Structured Data Linter.
100

Progressive Web App

Indicates how valid the aspects of a Progressive Web App (PWA) are for the page and highlights opportunities to enable/improve the PWA of disruptive.asia. This includes details about web app manifests.

Installable

Web app manifest and service worker meet the installability requirements
User engagement may be increased by leveraging the browsers ability to proactively prompt users to add the app to their homescreen.

PWA Optimized

Registers a service worker that controls page and `start_url`
A service worker is used to provide Progressive Web Apps the use of features such as working offline, the ability for the app to be added to the homescreen as well as push notifications.
Redirects HTTP traffic to HTTPS
It is advised to redirect all HTTP traffic to HTTPS, in order to enable secure web features for all users.
Configured for a custom splash screen
Themed splash screens ensure a high-quality user experience at launch for app users.
View Data
Sets a theme color for the address bar.
A theme may be applied to the browser address bar, which ideally can be made to match the site.
View Data
Content is sized correctly for the viewport
Ensure that the width of the app's content matches the width of the viewport, otherwise the app might not be optimized for mobile screens.
Has a `<meta name="viewport">` tag with `width` or `initial-scale`
It is advised to use a '<meta name="viewport">' tag for the optimization of disruptive.asia on mobile screens.
Provides a valid `apple-touch-icon`
iOS users of Progressive Web Apps will benefit from an apple touch icon, which can be defined with 'apple-touch-icon', which must point to a non-transparent 192px (or 180px) square PNG.
Manifest has a maskable icon
Maskable icons are great to ensure that images fill the entire shape when installing the app on a device.

Manual Checks

Site works cross-browser
Ensure that the Progressive Web App works correctly across every major browser.
Page transitions don't feel like they block on the network
Users perceive apps with responsive, snappy transitions as higher peforming and ensures a great user experience, even on a slow network.
Each page has a URL
Ensure that all pages are deep linkable via URL. They should also be unique for the purpose of shareability on social media.
Hosting

Server Location

Server IP Address: 35.195.187.5
Continent: Europe
Country: Belgium
Belgium Flag
Region: Brussels Capital
City: Brussels
Longitude: 4.3337
Latitude: 50.8336
Currencies: EUR
Languages: German
French
Dutch

Web Hosting Provider

Name IP Address
Google LLC
Registration

Domain Registrant

Private Registration: No
Name:
Organization:
Country:
City:
State:
Post Code:
Email:
Phone:
Note: Registration information is derived from various sources and may be inaccurate.

Domain Registrar

Name IP Address
Domain.com, LLC 104.18.42.197
Security

Visitor Safety

Mature Content: Not Likely
McAfee WebAdvisor Rating: Safe
WOT Rating:
WOT Trustworthiness:
WOT Child Safety:
Note: Safety information is not guaranteed.

SSL/TLS Certificate

Issued To: disruptive.asia
Issued By: R3
Valid From: 26th March, 2021
Valid To: 24th June, 2021
Subject: CN = disruptive.asia
Hash: 0207fede
Issuer: CN = R3
O = Let's Encrypt
S = US
Version: 2
Serial Number: 0x04914B1E9D95DE0B6A38A269A1D169996063
Serial Number (Hex): 04914B1E9D95DE0B6A38A269A1D169996063
Valid From: 26th March, 2024
Valid To: 24th June, 2024
Signature Algorithm (Short Name): RSA-SHA256
Signature Algorithm (Long Name): sha256WithRSAEncryption
Authority Key Identifier: keyid:14:2E:B3:17:B7:58:56:CB:AE:50:09:40:E6:1F:AF:9D:8B:14:C2:C6
Extended Key Usage: TLS Web Server Authentication, TLS Web Client Authentication
Certificate Policies: Policy: 2.23.140.1.2.1
Policy: 1.3.6.1.4.1.44947.1.1.1
CPS: http://cps.letsencrypt.org

Authority Information Access: OCSP - URI:http://r3.o.lencr.org
CA Issuers - URI:http://r3.i.lencr.org/

SCT List: Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 94:20:BC:1E:8E:D5:8D:6C:88:73:1F:82:8B:22:2C:0D:
D1:DA:4D:5E:6C:4F:94:3D:61:DB:4E:2F:58:4D:A2:C2
Timestamp : Mar 26 12:24:49.228 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:49:5A:45:31:9E:89:DD:F6:01:82:86:DE:
15:ED:31:46:67:D2:7C:96:D6:F3:B9:8B:AF:14:CD:08:
19:7B:62:E6:02:20:0B:E2:D4:2C:0F:3F:86:CB:61:FC:
4A:D0:A7:1F:CD:FB:CE:AA:B0:30:B5:A9:25:40:66:86:
A4:C7:54:04:89:4E
Signed Certificate Timestamp:
Version : v1 (0x0)
Log ID : 7D:3E:F2:F8:8F:FF:88:55:68:24:C2:C0:CA:9E:52:89:
79:2B:C5:0E:78:09:7F:2E:6A:97:68:99:7E:22:F0:D7
Timestamp : Mar 26 12:24:49.270 2021 GMT
Extensions: none
Signature : ecdsa-with-SHA256
30:44:02:20:15:52:F6:70:0F:AC:6D:ED:E1:CF:A6:61:
5C:FD:04:D2:A7:EE:E5:DD:37:6A:64:6D:1B:56:E2:36:
E1:B9:ED:77:02:20:70:24:14:CA:D8:39:D6:10:B2:06:
6F:6B:EA:E9:A5:C5:AE:51:DA:31:8D:7C:0C:62:BF:24:
F1:19:8F:B4:0B:3B
Key Usage: Digital Signature, Key Encipherment
Basic Constraints: CA:FALSE
Subject Alternative Name: DNS:disruptive.asia
Technical

DNS Lookup

A Records

Host IP Address Class TTL
disruptive.asia. 35.195.187.5 IN 3599

NS Records

Host Nameserver Class TTL
disruptive.asia. ns1.ipage.com. IN 3599
disruptive.asia. ns2.ipage.com. IN 3599

MX Records

Priority Host Server Class TTL
30 disruptive.asia. mx.disruptive.asia. IN 3599

SOA Records

Domain Name Primary NS Responsible Email TTL
disruptive.asia. ns1.ipage.com. dnsadmin.ipage.com. 3599

TXT Records

Host Value Class TTL
disruptive.asia. v=spf1 IN 3599

HTTP Response Headers

HTTP-Code: HTTP/1.1 200 OK
Server: nginx
Date: 30th March, 2021
Content-Type: text/html; charset=UTF-8
Cache-Control: max-age=600, must-revalidate
Content-Length: 185474
Connection: keep-alive
Keep-Alive: timeout=20
Vary: Accept-Encoding,Cookie
Link: <https://wp.me/P7GN6f-5>; rel=shortlink
X-Powered-By: WP Engine
X-Cacheable: SHORT
X-Cache: HIT
X-Cache-Group: normal
Accept-Ranges: bytes

Whois Lookup

Created: 6th February, 2016
Changed: 5th May, 2020
Expires: 6th February, 2021
Registrar: Domain.com, LLC
Status: clientTransferProhibited
clientUpdateProhibited
Nameservers: ns1.ipage.com
ns2.ipage.com
Owner Organization: Data Protected
Owner State: ON
Owner Country: CA
Full Whois: Domain Name: DISRUPTIVE.ASIA
Registry Domain ID: D107700000004646338-AGRS
Registrar WHOIS Server:
Registrar URL: www.domain.com
Updated Date: 2020-05-05T23:45:10Z
Creation Date: 2016-06-02T10:31:21Z
Registry Expiry Date: 2021-06-02T10:31:21Z
Registrar Registration Expiration Date:
Registrar: Domain.com, LLC
Registrar IANA ID: 886
Registrar Abuse Contact Email:
Registrar Abuse Contact Phone:
Reseller:
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited
Registrant Organization: Data Protected
Registrant State/Province: ON
Registrant Country: CA
Name Server: NS1.IPAGE.COM
Name Server: NS2.IPAGE.COM
DNSSEC: unsigned
URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of WHOIS database: 2021-03-30T05:37:45Z <<<

For more information on Whois status codes, please visit https://icann.org/epp

Access to WHOIS information is provided to assist persons in determining the contents of a domain name registration record in the registry database. The data in this record is provided by The Registry Operator for informational purposes only, and accuracy is not guaranteed. This service is intended only for query-based access. You agree that you will use this data only for lawful purposes and that, under no circumstances will you use this data to (a) allow, enable, or otherwise support the transmission by e-mail, telephone, or facsimile of mass unsolicited, commercial advertising or solicitations to entities other than the data recipient's own existing customers; or (b) enable high volume, automated, electronic processes that send queries or data to the systems of Registry Operator, a Registrar, or Afilias except as reasonably necessary to register domain names or modify existing registrations. All rights reserved. Registry Operator reserves the right to modify these terms at any time. By submitting this query, you agree to abide by this policy.
The Registrar of Record identified in this output may have an RDDS service that can be queried for additional information on how to contact the Registrant, Admin, or Tech contact of the queried domain name.

Nameservers

Name IP Address
ns1.ipage.com 66.96.142.163
ns2.ipage.com 65.254.254.151
Related

Subdomains

Similar Sites

Organic Search (US) Competitors

Backlink Competitors

Sites with the same domain name

Domain Valuation Snoop Score
0/5
0/5
0/5
0/5

Sites hosted on the same IP address

Domain Valuation Snoop Score
0/5
$3,857 USD 3/5