2.9 sec in total
34 ms
2.3 sec
560 ms
Welcome to pentaho.org homepage info - get ready to check Pentaho best content for Russia right away, or after learning these important things about pentaho.org
With battle-tested solutions and a focus on foundational strength, Pentaho+ helps you meet the challenges of an AI-driven world.
Visit pentaho.orgWe analyzed Pentaho.org page load time and found that the first response time was 34 ms and then it took 2.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.
pentaho.org performance score
name
value
score
weighting
Value4.8 s
11/100
10%
Value13.6 s
0/100
25%
Value8.0 s
22/100
10%
Value1,290 ms
18/100
30%
Value0
100/100
15%
Value12.7 s
13/100
10%
34 ms
696 ms
70 ms
137 ms
182 ms
Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Pentaho.org, 70% (50 requests) were made to Pentaho.com and 7% (5 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (696 ms) relates to the external source Pentaho.com.
Page size can be reduced by 269.9 kB (13%)
2.0 MB
1.8 MB
In fact, the total size of Pentaho.org main page is 2.0 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. 70% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.
Potential reduce by 93.0 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 34.4 kB, which is 32% 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 93.0 kB or 86% of the original size.
Potential reduce by 83.2 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. Pentaho images are well optimized though.
Potential reduce by 88.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 88.2 kB or 21% of the original size.
Potential reduce by 5.5 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. Pentaho.org has all CSS files already compressed.
Number of requests can be reduced by 30 (56%)
54
24
The browser has sent 54 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 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 19 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
pentaho.org
34 ms
pentaho.com
696 ms
style.min.css
70 ms
styles.css
137 ms
style.css
182 ms
custom-style.css
187 ms
header-style.css
193 ms
bootstrap.min.css
260 ms
all.min.css
44 ms
bootstrap-icons.min.css
55 ms
neue-haas-grotesk-display-pro-font.css
191 ms
swiper-bundle.min.css
39 ms
aos.css
51 ms
jquery.min.js
209 ms
jquery-migrate.min.js
247 ms
script.js
251 ms
pintra-redirect.js
324 ms
cookiebot.css
255 ms
uc.js
59 ms
api.js
56 ms
index.js
277 ms
index.js
308 ms
player.js
58 ms
custom-script.js
314 ms
popper.min.js
47 ms
bootstrap.min.js
428 ms
swiper-bundle.min.js
42 ms
jquery.validate.min.js
39 ms
aos.js
60 ms
aos.css
26 ms
aos.js
12 ms
aos.css
14 ms
neue-haas-grotesk-display-pro-font.css
148 ms
gtm.js
104 ms
939184272
127 ms
Logo.png
93 ms
home-hero.jpeg
279 ms
4.png
190 ms
5.png
277 ms
1.png
92 ms
6.png
278 ms
3.png
277 ms
2.png
174 ms
3.webp
277 ms
2.webp
277 ms
1.jpg
278 ms
PDA.png
470 ms
linkedin.svg
290 ms
facebook.svg
297 ms
twitter.svg
308 ms
youtube.svg
320 ms
recaptcha__en.js
114 ms
customer-story-1-compressed.jpg
298 ms
arrow-left.svg
313 ms
arrow-right.svg
321 ms
email-capture-compressed.jpg
392 ms
cta-compressed.jpg
400 ms
footer.png
365 ms
NeueHaasDisplayLight.woff
379 ms
NeueHaasDisplayBlack.ttf
456 ms
NeueHaasDisplayRoman.woff
430 ms
NeueHaasDisplayThin.woff
456 ms
NeueHaasDisplayXThin.woff
457 ms
NeueHaasDisplayXXThin.woff
471 ms
NeueHaasDisplayMediu.woff
495 ms
NeueHaasDisplayBold.woff
507 ms
NeueHaasDisplayBlack.woff
527 ms
NeueHaasDisplayRoman.ttf
578 ms
js
61 ms
46149
312 ms
46149
74 ms
pentaho.org 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
Buttons do not have an accessible name
Links do not have a discernible name
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 IDs are not unique
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
pentaho.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
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pentaho.org SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pentaho.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 Pentaho.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.
pentaho.org
Open Graph data is detected on the main page of Pentaho. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: