Tools & Wizards About Us
plumelabs.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

plumelabs.com

Plume Labs | Be Empowered Against Air Pollution

Page Load Speed

3.9 sec in total

First Response

467 ms

Resources Loaded

2.5 sec

Page Rendered

914 ms

plumelabs.com screenshot

About Website

Welcome to plumelabs.com homepage info - get ready to check Plume Labs best content for United States right away, or after learning these important things about plumelabs.com

Plume Labs helps you understand what you breathe and take meaningful action against air pollution. We are the makers of Flow, the first personal air quality tracker and of AIR, the pollution forecasti...

Visit plumelabs.com

Key Findings

We analyzed Plumelabs.com page load time and found that the first response time was 467 ms and then it took 3.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

plumelabs.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

31/100

10%

LCP (Largest Contentful Paint)

Value14.1 s

0/100

25%

SI (Speed Index)

Value7.0 s

32/100

10%

TBT (Total Blocking Time)

Value3,590 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value18.1 s

3/100

10%

Network Requests Diagram

plumelabs.com

467 ms

css

102 ms

bootstrap.min.css

72 ms

main-2016012515.css

204 ms

banner-2016012515.css

255 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 32% of them (29 requests) were addressed to the original Plumelabs.com, 23% (21 requests) were made to A.tiles.mapbox.com and 22% (20 requests) were made to B.tiles.mapbox.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Plumelabs.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 438.8 kB (20%)

Content Size

2.2 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 42.2 kB

  • Original 51.6 kB
  • After minification 48.0 kB
  • After compression 9.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 42.2 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 29.8 kB

  • Original 1.6 MB
  • After minification 1.6 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. Plume Labs images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 262.3 kB

  • Original 426.9 kB
  • After minification 420.7 kB
  • After compression 164.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 262.3 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 104.5 kB

  • Original 126.6 kB
  • After minification 124.0 kB
  • After compression 22.0 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. Plumelabs.com needs all CSS files to be minified and compressed as it can save up to 104.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (34%)

Requests Now

89

After Optimization

59

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 89 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Plume Labs. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

plumelabs.com

plumelabs.com

467 ms

css

css

102 ms

bootstrap.min.css

bootstrap.min.css

72 ms

main-2016012515.css

main-2016012515.css

204 ms

banner-2016012515.css

banner-2016012515.css

255 ms

jquery.min.js

jquery.min.js

120 ms

mapbox.js

mapbox.js

96 ms

mapbox.css

mapbox.css

96 ms

classic-081711.css

classic-081711.css

86 ms

mc-validate.js

mc-validate.js

121 ms

bootstrap.min.js

bootstrap.min.js

93 ms

map.js

map.js

391 ms

producthunt.png

producthunt.png

508 ms

apple-circle.png

apple-circle.png

149 ms

google-circle.png

google-circle.png

137 ms

plumelabs.png

plumelabs.png

389 ms

city.jpg

city.jpg

849 ms

iphone-app.gif

iphone-app.gif

994 ms

app-store.png

app-store.png

457 ms

play-store.png

play-store.png

290 ms

know-what-you-breathe.png

know-what-you-breathe.png

483 ms

protect-yourself.png

protect-yourself.png

491 ms

stay-ahead.png

stay-ahead.png

633 ms

air-report.jpg

air-report.jpg

1466 ms

techcrunch.png

techcrunch.png

653 ms

thenewyorktimes.jpg

thenewyorktimes.jpg

697 ms

thewallstreetjournal.jpg

thewallstreetjournal.jpg

776 ms

thewashingtonpost.jpg

thewashingtonpost.jpg

863 ms

mittechnologyreview.png

mittechnologyreview.png

834 ms

lemonde.png

lemonde.png

1072 ms

lesechos.png

lesechos.png

1013 ms

challenges.jpg

challenges.jpg

944 ms

france24.png

france24.png

971 ms

thinkprogress.png

thinkprogress.png

1151 ms

line-shadow.png

line-shadow.png

1093 ms

presskit.png

presskit.png

1087 ms

theytalkaboutus.png

theytalkaboutus.png

1141 ms

JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf

JbtMzqLaYbbbCL9X6EvaIy3USBnSvpkopQaUR-2r7iU.ttf

164 ms

-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf

-_Ctzj9b56b8RgXW8FAriS3USBnSvpkopQaUR-2r7iU.ttf

214 ms

analytics.js

analytics.js

142 ms

widgets.js

widgets.js

64 ms

sdk.js

sdk.js

88 ms

plumemapbox.fcca966f.json

plumemapbox.fcca966f.json

448 ms

icons-000000@2x.png

icons-000000@2x.png

29 ms

21_newPI_MACCHybrid_SA.png

21_newPI_MACCHybrid_SA.png

535 ms

button.831500944bc3eb7ea5276ccdc3f71d2e.js

button.831500944bc3eb7ea5276ccdc3f71d2e.js

38 ms

115 ms

xd_arbiter.php

xd_arbiter.php

90 ms

follow_button.6a78875565a912489e9aef879c881358.en.html

follow_button.6a78875565a912489e9aef879c881358.en.html

57 ms

collect

collect

71 ms

info.json

info.json

96 ms

3.png

3.png

427 ms

3.png

3.png

281 ms

2.png

2.png

397 ms

4.png

4.png

404 ms

3.png

3.png

364 ms

2.png

2.png

373 ms

4.png

4.png

416 ms

1.png

1.png

583 ms

5.png

5.png

700 ms

1.png

1.png

614 ms

3.png

3.png

406 ms

5.png

5.png

687 ms

2.png

2.png

418 ms

4.png

4.png

427 ms

1.png

1.png

726 ms

5.png

5.png

743 ms

3.png

3.png

851 ms

2.png

2.png

969 ms

4.png

4.png

744 ms

1.png

1.png

1098 ms

5.png

5.png

745 ms

2.png

2.png

388 ms

4.png

4.png

400 ms

3.png

3.png

367 ms

2.png

2.png

370 ms

4.png

4.png

388 ms

1.png

1.png

682 ms

5.png

5.png

653 ms

1.png

1.png

706 ms

3.png

3.png

407 ms

5.png

5.png

719 ms

2.png

2.png

706 ms

4.png

4.png

424 ms

1.png

1.png

733 ms

5.png

5.png

985 ms

3.png

3.png

992 ms

2.png

2.png

1037 ms

4.png

4.png

728 ms

1.png

1.png

1056 ms

5.png

5.png

1070 ms

jot.html

jot.html

2 ms

Accessibility Review

plumelabs.com accessibility score

63

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Form elements do not have associated labels

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

plumelabs.com best practices score

83

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

SEO Factors

plumelabs.com SEO score

91

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

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 Plumelabs.com 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 Plumelabs.com 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

plumelabs.com

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