Tools & Wizards About Us
plume.io screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

plume.io

Plume Labs API: Accurate live and forecast air quality data

Page Load Speed

1.9 sec in total

First Response

142 ms

Resources Loaded

1.2 sec

Page Rendered

577 ms

plume.io screenshot

About Website

Visit plume.io now to see the best up-to-date Plume content for United States and also check out these interesting facts you probably never knew about plume.io

Integrate Plume Labs' highly flexible APIs & start taking advantage of accurate real-time, forecast & historical air quality information for your business.

Visit plume.io

Key Findings

We analyzed Plume.io page load time and found that the first response time was 142 ms and then it took 1.8 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

plume.io performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

56/100

10%

LCP (Largest Contentful Paint)

Value7.7 s

3/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

plume.io

142 ms

170 ms

snippet.js

31 ms

polyfill-a89574f1ffba058b968a.js

328 ms

component---src-pages-forecast-api-js-89e3f5ff271de940cc8c.js

217 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Plume.io, 89% (24 requests) were made to Plumelabs.com and 4% (1 request) were made to Static.zdassets.com. The less responsive or slowest element that took the longest time to load (407 ms) relates to the external source Plumelabs.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 119.5 kB (24%)

Content Size

493.5 kB

After Optimization

374.0 kB

  • HTML
  • JavaScript

In fact, the total size of Plume.io main page is 493.5 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 30% of websites need less resources to load. Javascripts take 322.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 119.4 kB

  • Original 170.9 kB
  • After minification 170.7 kB
  • After compression 51.4 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 119.4 kB or 70% of the original size.

JavaScript Optimization

-0%

Potential reduce by 32 B

  • Original 322.6 kB
  • After minification 322.6 kB
  • After compression 322.6 kB

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

Requests Breakdown

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

Requests Now

16

After Optimization

3

  • AJAX
  • JavaScript

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

Network Requests Diagram

plume.io

plume.io

142 ms

170 ms

snippet.js

snippet.js

31 ms

polyfill-a89574f1ffba058b968a.js

polyfill-a89574f1ffba058b968a.js

328 ms

component---src-pages-forecast-api-js-89e3f5ff271de940cc8c.js

component---src-pages-forecast-api-js-89e3f5ff271de940cc8c.js

217 ms

ce103cd9a527f394c47573da4f6eee2e84b8bdbd-4cb9947bc716944613dd.js

ce103cd9a527f394c47573da4f6eee2e84b8bdbd-4cb9947bc716944613dd.js

217 ms

6ddaa806f858c0cc5ddccad46cc48c9a68e0d5b7-858760cdc7c7bf79c7c6.js

6ddaa806f858c0cc5ddccad46cc48c9a68e0d5b7-858760cdc7c7bf79c7c6.js

213 ms

c76cb08fc30e22208a20e758b68bce9093d86a91-a00d333ed323cc39a835.js

c76cb08fc30e22208a20e758b68bce9093d86a91-a00d333ed323cc39a835.js

217 ms

7188a954071398aca4758dd40ffc3e8b516e66a7-b3008b34b7ebff7a38ce.js

7188a954071398aca4758dd40ffc3e8b516e66a7-b3008b34b7ebff7a38ce.js

180 ms

commons-fee27da139fa068b9684.js

commons-fee27da139fa068b9684.js

372 ms

styles-e9d24b1846c7d6eb9685.js

styles-e9d24b1846c7d6eb9685.js

407 ms

app-03909461c7adca295e65.js

app-03909461c7adca295e65.js

399 ms

framework-05e9a5e21a5e79698b07.js

framework-05e9a5e21a5e79698b07.js

382 ms

webpack-runtime-427d19fb87b0a064d3aa.js

webpack-runtime-427d19fb87b0a064d3aa.js

344 ms

gtm.js

gtm.js

86 ms

Gilroy-Bold-ab923fcb428143852fdbd0c383c35783.woff

Gilroy-Bold-ab923fcb428143852fdbd0c383c35783.woff

172 ms

Gilroy-ExtraBold-045c648406ffe18c0c8c510a235440d9.woff

Gilroy-ExtraBold-045c648406ffe18c0c8c510a235440d9.woff

200 ms

Gilroy-Black-e312bd0354f5de08ea18a4252463e80f.woff

Gilroy-Black-e312bd0354f5de08ea18a4252463e80f.woff

230 ms

Gilroy-SemiBold-7239a1c7033aa420e2ada6f861faf1db.woff

Gilroy-SemiBold-7239a1c7033aa420e2ada6f861faf1db.woff

175 ms

Gilroy-Medium-f32393e6c6fcbb7b958b97dc7f4535f5.woff

Gilroy-Medium-f32393e6c6fcbb7b958b97dc7f4535f5.woff

242 ms

Gilroy-Regular-759b570310ed95778afe261a2d33b212.woff

Gilroy-Regular-759b570310ed95778afe261a2d33b212.woff

242 ms

Gilroy-Light-3779263564ee229012cfc2e437dd9deb.woff

Gilroy-Light-3779263564ee229012cfc2e437dd9deb.woff

359 ms

Gilroy-ExtraLight-14a2f1156e4ef0e1a1527c1b95894030.woff

Gilroy-ExtraLight-14a2f1156e4ef0e1a1527c1b95894030.woff

346 ms

Gilroy-Thin-6c00516d6eedf9c22bd352524547c8e1.woff

Gilroy-Thin-6c00516d6eedf9c22bd352524547c8e1.woff

360 ms

32-f05d16aaa539e4f7a9f9.js

32-f05d16aaa539e4f7a9f9.js

400 ms

app-data.json

app-data.json

281 ms

page-data.json

page-data.json

314 ms

Accessibility Review

plume.io accessibility score

75

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

plume.io best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

plume.io SEO score

91

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 Plume.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 Plume.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

plume.io

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