Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

potree.org

GitHub - potree/potree: WebGL point cloud viewer for large datasets

Page Load Speed

706 ms in total

First Response

326 ms

Resources Loaded

328 ms

Page Rendered

52 ms

About Website

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

WebGL point cloud viewer for large datasets. Contribute to potree/potree development by creating an account on GitHub.

Visit potree.org

Key Findings

We analyzed Potree.org page load time and found that the first response time was 326 ms and then it took 380 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

potree.org performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

40/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value7.5 s

26/100

10%

TBT (Total Blocking Time)

Value950 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value13.4 s

11/100

10%

Network Requests Diagram

potree.org

326 ms

Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Potree.org and no external sources were called. The less responsive or slowest element that took the longest time to load (326 ms) belongs to the original domain Potree.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 399.3 kB (31%)

Content Size

1.3 MB

After Optimization

891.5 kB

In fact, the total size of Potree.org main page is 1.3 MB. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. Images take 773.4 kB which makes up the majority of the site volume.

HTML Optimization

-15%

Potential reduce by 18 B

  • Original 122 B
  • After minification 119 B
  • After compression 104 B

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 18 B or 15% of the original size.

Image Optimization

-1%

Potential reduce by 8.5 kB

  • Original 773.4 kB
  • After minification 764.9 kB

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. Potree images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 138.2 kB

  • Original 214.6 kB
  • After minification 214.5 kB
  • After compression 76.4 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 138.2 kB or 64% of the original size.

CSS Optimization

-83%

Potential reduce by 252.6 kB

  • Original 302.7 kB
  • After minification 285.5 kB
  • After compression 50.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. Potree.org needs all CSS files to be minified and compressed as it can save up to 252.6 kB or 83% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Accessibility Review

potree.org accessibility score

84

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-*] attributes do not match their roles

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

potree.org 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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

potree.org SEO score

84

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

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Potree.org can be misinterpreted by Google and other search engines. Our service has detected that English 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 Potree.org main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

Open Graph description is not detected on the main page of Potree. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: