Tools & Wizards About Us
emqx.io screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    40% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 90% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    82% of websites

  • 89

    SEO

    Google-friendlier than
    67% of websites

emqx.io

EMQX: The World's #1 Open Source Distributed MQTT Broker

Page Load Speed

8 sec in total

First Response

469 ms

Resources Loaded

4.3 sec

Page Rendered

3.3 sec

emqx.io screenshot

About Website

Visit emqx.io now to see the best up-to-date EMQX content for China and also check out these interesting facts you probably never knew about emqx.io

EMQX: The most scalable MQTT Broker for IoT. Connect 100M+ IoT devices in 1 cluster at 1ms latency. Move and process millions of MQTT messages per second.

Visit emqx.io

Key Findings

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

Performance Metrics

emqx.io performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.2 s

8/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value9.3 s

13/100

10%

TBT (Total Blocking Time)

Value12,320 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.055

98/100

15%

TTI (Time to Interactive)

Value21.5 s

1/100

10%

Network Requests Diagram

emqx.io

469 ms

www.emqx.io

1265 ms

5bc5ca7.css

874 ms

2498019.css

915 ms

775465f.css

895 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 9% of them (3 requests) were addressed to the original Emqx.io, 78% (25 requests) were made to Emqxio-static.emqx.net and 9% (3 requests) were made to Assets.emqx.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Emqxio-static.emqx.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 665.0 kB (29%)

Content Size

2.3 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Emqx.io main page is 2.3 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. 70% of websites need less resources to load. Images take 2.1 MB which makes up the majority of the site volume.

HTML Optimization

-59%

Potential reduce by 46.1 kB

  • Original 78.7 kB
  • After minification 76.9 kB
  • After compression 32.6 kB

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

Image Optimization

-29%

Potential reduce by 618.7 kB

  • Original 2.1 MB
  • After minification 1.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, EMQX needs image optimization as it can save up to 618.7 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 58 B

  • Original 25.2 kB
  • After minification 25.2 kB
  • After compression 25.2 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 122 B

  • Original 77.2 kB
  • After minification 77.2 kB
  • After compression 77.1 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. Emqx.io has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (48%)

Requests Now

29

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

emqx.io

emqx.io

469 ms

www.emqx.io

www.emqx.io

1265 ms

5bc5ca7.css

5bc5ca7.css

874 ms

2498019.css

2498019.css

915 ms

775465f.css

775465f.css

895 ms

6d30e6d.css

6d30e6d.css

890 ms

278bc7f.css

278bc7f.css

909 ms

2c002854542957312f748db7e6289a20.png

2c002854542957312f748db7e6289a20.png

987 ms

state.js

state.js

985 ms

92c4e42.js

92c4e42.js

969 ms

341df03.js

341df03.js

970 ms

fb0a3a9.js

fb0a3a9.js

971 ms

f97743f.js

f97743f.js

991 ms

cd13254.js

cd13254.js

969 ms

771218c.js

771218c.js

1378 ms

0d6a408.js

0d6a408.js

1068 ms

9e81763.js

9e81763.js

970 ms

iconfont.css

iconfont.css

971 ms

animate.min.css

animate.min.css

55 ms

running-cloud-en.fdb7546.png

running-cloud-en.fdb7546.png

1374 ms

features-1.11c58f6.png

features-1.11c58f6.png

1451 ms

features-2.cf933c9.png

features-2.cf933c9.png

1374 ms

features-4-1.43d1090.png

features-4-1.43d1090.png

1449 ms

features-4-2.3ab521f.png

features-4-2.3ab521f.png

1452 ms

features-4-3.4163bb0.png

features-4-3.4163bb0.png

1451 ms

logo.png

logo.png

235 ms

97e45e3ffab7df2ac94f8ac4ec25f037.png

97e45e3ffab7df2ac94f8ac4ec25f037.png

964 ms

edf8d8bb803343d51cd96196d31c27ee.png

edf8d8bb803343d51cd96196d31c27ee.png

1412 ms

runing-cloud-bg.a8fcac6.png

runing-cloud-bg.a8fcac6.png

386 ms

running-environment-bg.f39ec0a.png

running-environment-bg.f39ec0a.png

391 ms

icon-play.005cbe3.png

icon-play.005cbe3.png

391 ms

iconfont.woff

iconfont.woff

942 ms

Accessibility Review

emqx.io accessibility score

96

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

Heading elements are not in a sequentially-descending order

Best Practices

emqx.io best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

emqx.io SEO score

89

Search Engine Optimization Advices

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Emqx.io can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Emqx.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

emqx.io

Open Graph data is detected on the main page of EMQX. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: