Tools & Wizards About Us
iotw.io screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

iotw.io

IOTW - A Blockchain-Enabled IoT Data Unifying Platform

Page Load Speed

8.8 sec in total

First Response

19 ms

Resources Loaded

3.9 sec

Page Rendered

4.9 sec

iotw.io screenshot

About Website

Visit iotw.io now to see the best up-to-date IOTW content for Hong Kong and also check out these interesting facts you probably never knew about iotw.io

IOTW, a Big Data unifying system built on a native blockchain using Proof of Assignment (PoA) protocol, makes accessing data from a cross section of IoT devices and applications simple and efficient.

Visit iotw.io

Key Findings

We analyzed Iotw.io page load time and found that the first response time was 19 ms and then it took 8.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

iotw.io performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value9.3 s

12/100

10%

TBT (Total Blocking Time)

Value26,320 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value44.9 s

0/100

10%

Network Requests Diagram

iotw.io

19 ms

iotw.io

104 ms

gtm.js

108 ms

js

146 ms

main.css

177 ms

Our browser made a total of 150 requests to load all elements on the main page. We found that 84% of them (126 requests) were addressed to the original Iotw.io, 5% (8 requests) were made to Youtube.com and 2% (3 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Iotw.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (28%)

Content Size

3.7 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iotw.io main page is 3.7 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.9 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 73.1 kB

  • Original 83.3 kB
  • After minification 52.6 kB
  • After compression 10.2 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 30.6 kB, which is 37% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 73.1 kB or 88% of the original size.

Image Optimization

-14%

Potential reduce by 417.2 kB

  • Original 2.9 MB
  • After minification 2.5 MB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Obviously, IOTW needs image optimization as it can save up to 417.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-55%

Potential reduce by 111.8 kB

  • Original 201.6 kB
  • After minification 190.2 kB
  • After compression 89.8 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 111.8 kB or 55% of the original size.

CSS Optimization

-85%

Potential reduce by 426.4 kB

  • Original 500.1 kB
  • After minification 468.6 kB
  • After compression 73.6 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Iotw.io needs all CSS files to be minified and compressed as it can save up to 426.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (13%)

Requests Now

143

After Optimization

124

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 143 CSS, Javascripts, AJAX and image requests in order to completely render the main page of IOTW. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 17 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

iotw.io

iotw.io

19 ms

iotw.io

iotw.io

104 ms

gtm.js

gtm.js

108 ms

js

js

146 ms

main.css

main.css

177 ms

query.css

query.css

211 ms

aos.css

aos.css

364 ms

GfNczm-ZbgY

GfNczm-ZbgY

174 ms

TG-fixed.svg

TG-fixed.svg

620 ms

forbidden-mark-white.svg

forbidden-mark-white.svg

170 ms

cloud.jpg

cloud.jpg

618 ms

facebook.svg

facebook.svg

689 ms

twitter.svg

twitter.svg

625 ms

youtube.svg

youtube.svg

622 ms

TG.svg

TG.svg

693 ms

medium.svg

medium.svg

696 ms

linkedin.svg

linkedin.svg

688 ms

bitcoinbench.svg

bitcoinbench.svg

693 ms

arrow-down-filled-triangle.svg

arrow-down-filled-triangle.svg

690 ms

logo.svg

logo.svg

940 ms

music-player-play.svg

music-player-play.svg

929 ms

fred.png

fred.png

930 ms

Mask.svg

Mask.svg

930 ms

Path%203%20Copy.svg

Path%203%20Copy.svg

932 ms

Path%203.svg

Path%203.svg

937 ms

Proof.svg

Proof.svg

1207 ms

Micro.svg

Micro.svg

1084 ms

block.svg

block.svg

1002 ms

multi%20layer.svg

multi%20layer.svg

1075 ms

High-throughput.svg

High-throughput.svg

1079 ms

decentralized.svg

decentralized.svg

1122 ms

data-icon.svg

data-icon.svg

1102 ms

design-icon.svg

design-icon.svg

1227 ms

background%20shape%201.svg

background%20shape%201.svg

1162 ms

forbidden-mark.svg

forbidden-mark.svg

1257 ms

correct-symbol-white.svg

correct-symbol-white.svg

1191 ms

correct-symbol.svg

correct-symbol.svg

1263 ms

forbes%20Copy.svg

forbes%20Copy.svg

1448 ms

inverted-commas.svg

inverted-commas.svg

1371 ms

nasdaq.png

nasdaq.png

1312 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

1311 ms

48

48

812 ms

js

js

40 ms

analytics.js

analytics.js

75 ms

www-player.css

www-player.css

45 ms

www-embed-player.js

www-embed-player.js

208 ms

base.js

base.js

248 ms

fetch-polyfill.js

fetch-polyfill.js

41 ms

sliderNoTouch.js

sliderNoTouch.js

1199 ms

slider.js

slider.js

1261 ms

common.js

common.js

1303 ms

collect

collect

363 ms

main.js

main.js

1133 ms

aos.js

aos.js

904 ms

yahoo.png

yahoo.png

838 ms

enterpenur.png

enterpenur.png

958 ms

Calibri.ttf

Calibri.ttf

973 ms

ad_status.js

ad_status.js

272 ms

Oswald-Bold.ttf

Oswald-Bold.ttf

957 ms

Oswald-Extra-LightItalic.ttf

Oswald-Extra-LightItalic.ttf

909 ms

investopedia.png

investopedia.png

1009 ms

telegraph.png

telegraph.png

951 ms

shape%20IOTW.svg

shape%20IOTW.svg

985 ms

collect

collect

318 ms

ambcrypto.svg

ambcrypto.svg

999 ms

initplayback

initplayback

222 ms

embed.js

embed.js

54 ms

id

id

46 ms

BITCOIN-NEWS.png

BITCOIN-NEWS.png

754 ms

BITGURU.png

BITGURU.png

941 ms

blockonomi.svg

blockonomi.svg

837 ms

bitmanager.png

bitmanager.png

841 ms

chipin.svg

chipin.svg

873 ms

INVESTOPEDIA.png

INVESTOPEDIA.png

845 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

57 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

62 ms

Create

Create

32 ms

financemagnates.png

financemagnates.png

845 ms

ga-audiences

ga-audiences

69 ms

max%20keiser.svg

max%20keiser.svg

961 ms

NASDAQ.svg

NASDAQ.svg

1057 ms

newsmax.svg

newsmax.svg

943 ms

cryptoninjas.png

cryptoninjas.png

932 ms

cryptopotato.svg

cryptopotato.svg

919 ms

staker.svg

staker.svg

993 ms

townhall%20(2).svg

townhall%20(2).svg

879 ms

Group.svg

Group.svg

882 ms

zerohedge.svg

zerohedge.svg

896 ms

coinspeaker.svg

coinspeaker.svg

856 ms

GenerateIT

GenerateIT

16 ms

cryptodaily.svg

cryptodaily.svg

909 ms

crypto%20late.png

crypto%20late.png

955 ms

cryptovest.svg

cryptovest.svg

862 ms

garden.svg

garden.svg

924 ms

insider.png

insider.png

867 ms

Whitetiger.png

Whitetiger.png

878 ms

ikeyhome.png

ikeyhome.png

1198 ms

remotec_logo_2_large.svg

remotec_logo_2_large.svg

850 ms

gv.png

gv.png

1005 ms

poing95global%20copy.svg

poing95global%20copy.svg

1154 ms

bitgiant_1.png

bitgiant_1.png

853 ms

g2h2.png

g2h2.png

883 ms

logo-krypton-vertical.svg

logo-krypton-vertical.svg

824 ms

consta%20copy.svg

consta%20copy.svg

943 ms

compass.png

compass.png

868 ms

yorkshire.png

yorkshire.png

953 ms

bil.png

bil.png

1081 ms

motek.png

motek.png

978 ms

startup-500.jpg

startup-500.jpg

1045 ms

wine4112015.png

wine4112015.png

1200 ms

pythoncapital_white.png

pythoncapital_white.png

1125 ms

apac.jpg

apac.jpg

1021 ms

Ali.jpg

Ali.jpg

1049 ms

Berkeley.jpg

Berkeley.jpg

1169 ms

get

get

30 ms

realtek.jpg

realtek.jpg

1064 ms

FRED.png

FRED.png

1036 ms

RLowZH2Xcwtj3dY_yGSeKf8RcILu2Rj3JTO2BWyvP7U.js

RLowZH2Xcwtj3dY_yGSeKf8RcILu2Rj3JTO2BWyvP7U.js

5 ms

IN.svg

IN.svg

882 ms

marcin.png

marcin.png

1000 ms

peter.png

peter.png

1077 ms

tony.png

tony.png

1046 ms

patrick.png

patrick.png

1097 ms

hong.png

hong.png

1085 ms

TM@171x171.png

TM@171x171.png

1019 ms

Sum@171x171.png

Sum@171x171.png

1084 ms

gary.png

gary.png

1103 ms

chirstopher.png

chirstopher.png

1201 ms

joanne.png

joanne.png

1050 ms

cs.png

cs.png

1123 ms

tommy.png

tommy.png

1030 ms

fanny.png

fanny.png

1037 ms

Anthony.png

Anthony.png

1007 ms

jason.png

jason.png

1137 ms

Dean.png

Dean.png

1218 ms

AndrewBakst.png

AndrewBakst.png

1080 ms

yuen.png

yuen.png

1140 ms

Leslie.png

Leslie.png

1033 ms

Jeffrey%20A.%20Rinde.png

Jeffrey%20A.%20Rinde.png

1038 ms

Adam%20to.png

Adam%20to.png

1217 ms

dennisLam.png

dennisLam.png

1053 ms

Dr.%20Cong%20Wang.png

Dr.%20Cong%20Wang.png

959 ms

Tess.jpg

Tess.jpg

1125 ms

K%20B%20Chau%20&%20Co%20Solicitors.png

K%20B%20Chau%20&%20Co%20Solicitors.png

1024 ms

Upper%20background%20shape.svg

Upper%20background%20shape.svg

1044 ms

video%20place%20holder.png

video%20place%20holder.png

943 ms

Ecosystem.png

Ecosystem.png

1018 ms

background%20shape.svg

background%20shape.svg

1007 ms

footer%20shape.svg

footer%20shape.svg

952 ms

log_event

log_event

22 ms

Accessibility Review

iotw.io accessibility score

68

Accessibility Issues

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

iotw.io best practices score

58

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

iotw.io SEO score

75

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iotw.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Iotw.io main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

iotw.io

Open Graph description is not detected on the main page of IOTW. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: