919 ms in total
64 ms
748 ms
107 ms
Click here to check amazing Support Pentaho content for Australia. Otherwise, check out these important facts you probably never knew about support.pentaho.com
Visit support.pentaho.comWe analyzed Support.pentaho.com page load time and found that the first response time was 64 ms and then it took 855 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
support.pentaho.com performance score
name
value
score
weighting
Value2.6 s
64/100
10%
Value8.0 s
2/100
25%
Value5.0 s
63/100
10%
Value590 ms
51/100
30%
Value0.013
100/100
15%
Value7.8 s
45/100
10%
64 ms
175 ms
88 ms
36 ms
62 ms
Our browser made a total of 32 requests to load all elements on the main page. We found that 16% of them (5 requests) were addressed to the original Support.pentaho.com, 22% (7 requests) were made to Static.zdassets.com and 19% (6 requests) were made to Theme.zdassets.com. The less responsive or slowest element that took the longest time to load (175 ms) belongs to the original domain Support.pentaho.com.
Page size can be reduced by 89.2 kB (13%)
698.3 kB
609.1 kB
In fact, the total size of Support.pentaho.com main page is 698.3 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. 65% of websites need less resources to load. Images take 339.6 kB which makes up the majority of the site volume.
Potential reduce by 32.5 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 8.7 kB, which is 21% 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 32.5 kB or 79% of the original size.
Potential reduce by 56.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. Obviously, Support Pentaho needs image optimization as it can save up to 56.5 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 166 B
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.
Potential reduce by 34 B
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. Support.pentaho.com has all CSS files already compressed.
Number of requests can be reduced by 13 (59%)
22
9
The browser has sent 22 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Support Pentaho. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 11 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
support.pentaho.com
64 ms
support.pentaho.com
175 ms
hc
88 ms
en-us
36 ms
application-dabd91632e59b822715fbd3d678bb2b8.css
62 ms
theming_v1_support-e05586b61178dcde2a13a3d323525a18.css
72 ms
style.css
66 ms
jquery-09d07e20ce042ef10e301661ad1f316c.js
64 ms
css
60 ms
script.js
65 ms
en-us.8c89b1c5625d6133edf6.js
69 ms
without_iframe.js
103 ms
moment-4ef0d82f9fc65c8a28f659aa3430955f.js
58 ms
hc_enduser-aed5628a1a5251639e9960a1f9e080fa.js
171 ms
analytics.js
52 ms
gtm.js
95 ms
search-icon.png
93 ms
4d710da0c1e474e66f2599b7ff90f133f9326534.png
128 ms
561a3517efe3258931f1fb06f42a7df570de2003.png
122 ms
6015c56b6745ca3a77458ab1713f4f5bcf120000.webp
121 ms
768ac8cda3788ded09ca7b9c2a783f52ef024716.webp
120 ms
12577197b4216270ae43d7bbbcdd7b39add0ed07.png
134 ms
74386af76b6b2dd1e6763212f96397d84360a50a.webp
156 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
121 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
122 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
129 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
132 ms
host-without-iframe.js
76 ms
collect
47 ms
js
40 ms
js
98 ms
main.js
10 ms
support.pentaho.com 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
[role] values are not valid
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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
support.pentaho.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
support.pentaho.com 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Support.pentaho.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 Support.pentaho.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.
support.pentaho.com
Open Graph description is not detected on the main page of Support Pentaho. 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: