Tools & Wizards About Us
moss.earth screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

moss.earth

Moss: soluções de carbono de ponta a ponta

Page Load Speed

493 ms in total

First Response

92 ms

Resources Loaded

329 ms

Page Rendered

72 ms

moss.earth screenshot

About Website

Welcome to moss.earth homepage info - get ready to check Moss best content for Switzerland right away, or after learning these important things about moss.earth

A Moss usa tecnologia a favor da floresta. Descubra como protegemos a Amazônia com créditos de carbono e contribua compensando as emissões da sua empresa.

Visit moss.earth

Key Findings

We analyzed Moss.earth page load time and found that the first response time was 92 ms and then it took 401 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

moss.earth performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

17/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,010 ms

27/100

30%

CLS (Cumulative Layout Shift)

Value0.31

38/100

15%

TTI (Time to Interactive)

Value9.6 s

29/100

10%

Network Requests Diagram

moss.earth

92 ms

f4c9d39e64c0ae43.css

59 ms

polyfills-c67a75d1b6f99dc8.js

179 ms

webpack-2df7a8d27de1794c.js

73 ms

framework-114634acb84f8baa.js

170 ms

Our browser made a total of 11 requests to load all elements on the main page. We found that 91% of them (10 requests) were addressed to the original Moss.earth, 9% (1 request) were made to Static.cloudflareinsights.com. The less responsive or slowest element that took the longest time to load (200 ms) belongs to the original domain Moss.earth.

Page Optimization Overview & Recommendations

Page size can be reduced by 15.7 kB (10%)

Content Size

154.7 kB

After Optimization

139.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Moss.earth main page is 154.7 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. Only 5% of websites need less resources to load. Javascripts take 89.9 kB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 15.2 kB

  • Original 21.9 kB
  • After minification 21.9 kB
  • After compression 6.7 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 15.2 kB or 69% of the original size.

JavaScript Optimization

-0%

Potential reduce by 416 B

  • Original 89.9 kB
  • After minification 89.9 kB
  • After compression 89.5 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 75 B

  • Original 42.9 kB
  • After minification 42.9 kB
  • After compression 42.8 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. Moss.earth has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 8 (80%)

Requests Now

10

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

moss.earth

moss.earth

92 ms

f4c9d39e64c0ae43.css

f4c9d39e64c0ae43.css

59 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

179 ms

webpack-2df7a8d27de1794c.js

webpack-2df7a8d27de1794c.js

73 ms

framework-114634acb84f8baa.js

framework-114634acb84f8baa.js

170 ms

main-7209515590abf48c.js

main-7209515590abf48c.js

90 ms

_app-1dfdb684de55135f.js

_app-1dfdb684de55135f.js

78 ms

index-61aba610e4eac018.js

index-61aba610e4eac018.js

126 ms

_buildManifest.js

_buildManifest.js

200 ms

_ssgManifest.js

_ssgManifest.js

122 ms

v84a3a4012de94ce1a686ba8c167c359c1696973893317

v84a3a4012de94ce1a686ba8c167c359c1696973893317

75 ms

Accessibility Review

moss.earth accessibility score

81

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

Form elements do not have associated labels

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

Best Practices

moss.earth 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

moss.earth 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

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

Page is blocked from indexing

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

Language and Encoding

  • Language Detected

    PT

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Moss.earth can be misinterpreted by Google and other search engines. Our service has detected that Portuguese 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 Moss.earth 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

moss.earth

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