5.6 sec in total
89 ms
5.2 sec
306 ms
Click here to check amazing Pointools content. Otherwise, check out these important facts you probably never knew about pointools.com
Want to visualize, edit, and segment the largest point-cloud models while maintaining visual quality and accuracy? Try Bentley Pointools software.
Visit pointools.comWe analyzed Pointools.com page load time and found that the first response time was 89 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
pointools.com performance score
name
value
score
weighting
Value0.7 s
100/100
10%
Value0.7 s
100/100
25%
Value0.7 s
100/100
10%
Value0 ms
100/100
30%
Value0
100/100
15%
Value0.7 s
100/100
10%
89 ms
83 ms
146 ms
81 ms
54 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Pointools.com, 12% (12 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source B92.yahoo.co.jp.
Page size can be reduced by 641.6 kB (55%)
1.2 MB
534.4 kB
In fact, the total size of Pointools.com main page is 1.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. 65% of websites need less resources to load. Javascripts take 534.5 kB which makes up the majority of the site volume.
Potential reduce by 96.8 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. This page needs HTML code to be minified as it can gain 40.8 kB, which is 36% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 96.8 kB or 86% of the original size.
Potential reduce by 19.0 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. Pointools images are well optimized though.
Potential reduce by 323.0 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 323.0 kB or 60% of the original size.
Potential reduce by 202.9 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. Pointools.com needs all CSS files to be minified and compressed as it can save up to 202.9 kB or 86% of the original size.
Number of requests can be reduced by 36 (42%)
85
49
The browser has sent 85 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pointools. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
pointools
89 ms
pointools
83 ms
bentley-pointools
146 ms
css
81 ms
normalize.min.css
54 ms
styles.min.css
54 ms
jquery.fancybox.min.css
53 ms
carousel.min.css
53 ms
jquery.selectbox.min.css
61 ms
jquery.safari-checkbox.min.css
51 ms
jquery.mCustomScrollbar.min.css
67 ms
jquery-ui.min.css
65 ms
flexslider.min.css
68 ms
chosen.min.css
62 ms
jquery.bxslider.min.css
68 ms
jquery-1.10.2.min.js
68 ms
jquery-migrate-1.2.1.min.js
71 ms
VisitorIdentification.js
71 ms
jwplayer.js
129 ms
jscript.min.js
113 ms
jquery.flexslider-min.js
54 ms
jquery.caroufredsel.min.js
112 ms
jquery.selectbox-0.2.min.js
113 ms
jquery.checkbox.min.js
149 ms
jquery.mCustomScrollbar.concat.min.js
112 ms
jquery-ui.min.js
161 ms
jquery.fancybox.min.js
160 ms
chosen.jquery.min.js
159 ms
jquery.bxslider.min.js
254 ms
buttons.js
158 ms
conversion.js
51 ms
s_retargeting.js
1123 ms
09da084f09d470ad9e69abfabe17ef04.js
578 ms
Common.js
158 ms
s_code.js
157 ms
analytics.js
246 ms
fbds.js
229 ms
6b9f4cf9-56fe-4918-b64d-cfce7b4f3d43.js
264 ms
search-icon.png
207 ms
site_logo.png
206 ms
1699.ashx
210 ms
shadow.png
209 ms
771.ashx
272 ms
com-icon.png
206 ms
5007.ashx
295 ms
5720.ashx
297 ms
5055.ashx
295 ms
5058.ashx
311 ms
5062.ashx
295 ms
5086.ashx
343 ms
5090.ashx
361 ms
5099.ashx
361 ms
5121.ashx
361 ms
6506.ashx
337 ms
6377.ashx
358 ms
5387.ashx
360 ms
686.ashx
361 ms
8095.ashx
465 ms
2403.ashx
457 ms
2342.ashx
459 ms
1423.ashx
459 ms
3748.ashx
458 ms
Hgo13k-tfSpn0qi1SFdUfT8E0i7KZn-EPnyo3HZu7kw.woff
239 ms
vzIUHo9z-oJ4WgkpPOtg1_esZW2xOQ-xsNqO47m55DA.woff
263 ms
2UX7WLTfW3W8TclTUvlFyQ.woff
308 ms
RxZJdnzeo3R5zSexge8UUT8E0i7KZn-EPnyo3HZu7kw.woff
305 ms
d-6IYplOFocCacKzxwXSOD8E0i7KZn-EPnyo3HZu7kw.woff
306 ms
mnpfi9pxYH-Go5UiibESIj8E0i7KZn-EPnyo3HZu7kw.woff
308 ms
3776.ashx
448 ms
1391.ashx
526 ms
1361.ashx
524 ms
4560.ashx
490 ms
4555.ashx
487 ms
4197.ashx
485 ms
1855.ashx
481 ms
brochure-icon.png
515 ms
arrow.png
484 ms
social-icon-facebook.png
417 ms
social-icon-linkedin.png
419 ms
social-icon-twitter.png
417 ms
social-icon-youtube.png
373 ms
168 ms
collect
72 ms
88 ms
collect
90 ms
ga-audiences
18 ms
print.css
11 ms
jquery.min.js
166 ms
5007.ashx
128 ms
SalesContactHandler.ashx
155 ms
SalesContactHandler.ashx
148 ms
SalesContactHandler.ashx
172 ms
getAllAppDefault.esi
92 ms
7m8l7TlFO-S3VkhHuR0at4bN6UDyHWBl620a-IRfuBk.woff
16 ms
12mE4jfMSBTmg-81EiS-YRsxEYwM7FgeyaSgU71cLG0.woff
16 ms
1pO9eUAp8pSF8VnRTP3xnvesZW2xOQ-xsNqO47m55DA.woff
21 ms
OLffGBTaF0XFOW1gnuHF0YbN6UDyHWBl620a-IRfuBk.woff
16 ms
t6Nd4cfPRhZP44Q5QAjcC4bN6UDyHWBl620a-IRfuBk.woff
21 ms
bmC0pGMXrhphrZJmniIZpYbN6UDyHWBl620a-IRfuBk.woff
21 ms
getSegment.php
44 ms
s57645450935233
46 ms
t.dhj
69 ms
pointools.com accessibility score
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
Document doesn't have a <title> element
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [lang] attribute
pointools.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
pointools.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pointools.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Pointools.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.
pointools.com
Open Graph description is not detected on the main page of Pointools. 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: