Tools & Wizards About Us
emqx.io screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    60% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 50% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

emqx.io

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

Page Load Speed

6 sec in total

First Response

425 ms

Resources Loaded

4.9 sec

Page Rendered

650 ms

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 425 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

emqx.io performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.7 s

12/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.075

95/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

emqx.io

425 ms

www.emqx.io

1127 ms

gtm.js

49 ms

2663087.css

792 ms

b6c8368.css

574 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 303.6 kB (15%)

Content Size

2.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-67%

Potential reduce by 81.5 kB

  • Original 121.7 kB
  • After minification 119.8 kB
  • After compression 40.1 kB

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

Image Optimization

-14%

Potential reduce by 221.9 kB

  • Original 1.6 MB
  • After minification 1.3 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 221.9 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

-0%

Potential reduce by 150 B

  • Original 288.4 kB
  • After minification 288.4 kB
  • After compression 288.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.

Requests Breakdown

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

Requests Now

33

After Optimization

20

  • Images
  • JavaScript
  • CSS

The browser has sent 33 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 10 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

emqx.io

emqx.io

425 ms

www.emqx.io

www.emqx.io

1127 ms

gtm.js

gtm.js

49 ms

2663087.css

2663087.css

792 ms

b6c8368.css

b6c8368.css

574 ms

bd4b7b7.css

bd4b7b7.css

502 ms

logo.png

logo.png

233 ms

ce755b53dc44bb4c4614cee8dbec09c1.png

ce755b53dc44bb4c4614cee8dbec09c1.png

627 ms

state.js

state.js

1999 ms

b0cf40d.js

b0cf40d.js

463 ms

e32a699.js

e32a699.js

1988 ms

609d886.js

609d886.js

587 ms

883872d.js

883872d.js

648 ms

b6d4e43.js

b6d4e43.js

702 ms

4114ad1.js

4114ad1.js

788 ms

3d255b0.js

3d255b0.js

781 ms

iconfont.css

iconfont.css

816 ms

animate.min.css

animate.min.css

18 ms

iconfont.js

iconfont.js

901 ms

customer-logo-cisco.fc7d90e.png

customer-logo-cisco.fc7d90e.png

2015 ms

customer-logo-tsmc.74a6f28.png

customer-logo-tsmc.74a6f28.png

1987 ms

customer-logo-volkswagen.fea94ec.png

customer-logo-volkswagen.fea94ec.png

2454 ms

customer-logo-shell.7d7dac7.png

customer-logo-shell.7d7dac7.png

1991 ms

customer-logo-foxconn.1529644.png

customer-logo-foxconn.1529644.png

3107 ms

customer-logo-hewlettPackard.a2a4e72.png

customer-logo-hewlettPackard.a2a4e72.png

2798 ms

customer-logo-verifone.1143c33.png

customer-logo-verifone.1143c33.png

3334 ms

running-cloud-en.fdb7546.png

running-cloud-en.fdb7546.png

2200 ms

features-1.72a539a.png

features-1.72a539a.png

2159 ms

features-2.37f4d1f.png

features-2.37f4d1f.png

2336 ms

features-3.326acfc.png

features-3.326acfc.png

2350 ms

features-4.ec82c1a.png

features-4.ec82c1a.png

2454 ms

features-5.0fa6504.png

features-5.0fa6504.png

2438 ms

features-6.4c2f3d0.png

features-6.4c2f3d0.png

2589 ms

9b568e6f63de2fa44899594d0083f4d8.png

9b568e6f63de2fa44899594d0083f4d8.png

605 ms

ebb40812e5cad2bd90e6301f6b2d3f43.png

ebb40812e5cad2bd90e6301f6b2d3f43.png

627 ms

iconfont.woff

iconfont.woff

2455 ms

Accessibility Review

emqx.io accessibility score

80

Accessibility Issues

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

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

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

SEO Factors

emqx.io SEO score

82

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

Mobile Friendly

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

Impact

Issue

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: