6.4 sec in total
768 ms
3 sec
2.6 sec
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.orgWe analyzed Potree.org page load time and found that the first response time was 768 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.
potree.org performance score
name
value
score
weighting
Value3.4 s
37/100
10%
Value3.9 s
51/100
25%
Value9.7 s
11/100
10%
Value8,600 ms
0/100
30%
Value0
100/100
15%
Value15.6 s
6/100
10%
768 ms
158 ms
287 ms
270 ms
112 ms
Our browser made a total of 50 requests to load all elements on the main page. We found that 78% of them (39 requests) were addressed to the original Potree.org, 6% (3 requests) were made to S.ytimg.com and 4% (2 requests) were made to Stats.wordpress.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Potree.org.
Page size can be reduced by 447.7 kB (33%)
1.3 MB
900.1 kB
In fact, the total size of Potree.org main page is 1.3 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. 45% of websites need less resources to load. Images take 773.4 kB which makes up the majority of the site volume.
Potential reduce by 48.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 48.4 kB or 85% of the original size.
Potential reduce by 8.5 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.
Potential reduce by 138.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. 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.
Potential reduce by 252.6 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.
Number of requests can be reduced by 4 (9%)
46
42
The browser has sent 46 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Potree. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and as a result speed up the page load time.
potree.org
768 ms
style.css
158 ms
smc_front.css
287 ms
YJTCyY8Ch_w
270 ms
e-201613.js
112 ms
skybox-150x150.jpg
403 ms
distance_measure-150x150.jpg
406 ms
lions-150x150.jpg
404 ms
pix4d_online.jpg
797 ms
Harvest4D_logo.png
434 ms
github.png
406 ms
twitter.png
437 ms
e-201613.js
138 ms
www-embed-player-vfl-z2BtK.css
291 ms
www-embed-player.js
384 ms
base.js
1053 ms
background.gif
1537 ms
search.png
183 ms
comment-bubble.png
265 ms
lion_head.jpg
291 ms
chowilla.jpg
596 ms
eclepens.jpg
497 ms
heidentor.jpg
594 ms
CA13.jpg
913 ms
chiller.jpg
640 ms
ca13_300_300.jpg
826 ms
philly_300_300.jpg
1202 ms
maps_300_300.jpg
765 ms
matterhorn_300_300.jpg
811 ms
sigeom_300_300.jpg
917 ms
lion_300_300.jpg
951 ms
weiss_cooler_tower.jpg
960 ms
weiss_subsea_equipment.jpg
1462 ms
weiss_chiller.jpg
1189 ms
weiss_LDHI_module.jpg
1197 ms
weiss_lifeboat.jpg
1258 ms
weiss_subseamanifold.jpg
1205 ms
weiss_vessel.jpg
1250 ms
weiss_watertank.jpg
1456 ms
skatepark.jpg
1472 ms
pompei.jpg
1454 ms
lion.jpg
1454 ms
ecosynth.jpg
1694 ms
vienna_parliament_relief.jpg
1539 ms
tower.jpg
1793 ms
g.gif
104 ms
Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js
199 ms
ad_status.js
283 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
260 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
265 ms
potree.org accessibility score
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
[aria-*] attributes do not match their roles
[aria-hidden="true"] elements contain focusable descendents
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Image elements do not have [alt] attributes
Links do not have a discernible name
potree.org best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
potree.org SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
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 it matches the claimed language. Our system also found out that Potree.org 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.
potree.org
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: