2.5 sec in total
425 ms
1.9 sec
159 ms
Visit wiki.pentaho.com now to see the best up-to-date Wiki Pentaho content for Australia and also check out these interesting facts you probably never knew about wiki.pentaho.com
Welcome to the Pentaho Community wiki. This wiki contains documentation and information for the Pentaho Open Source BI Suite Community Edition (CE). The suite includes ETL http://en.wikipedia.org/wiki...
Visit wiki.pentaho.comWe analyzed Wiki.pentaho.com page load time and found that the first response time was 425 ms and then it took 2.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
wiki.pentaho.com performance score
name
value
score
weighting
Value4.7 s
13/100
10%
Value16.0 s
0/100
25%
Value8.8 s
16/100
10%
Value7,130 ms
0/100
30%
Value0.046
99/100
15%
Value25.7 s
0/100
10%
425 ms
81 ms
341 ms
81 ms
81 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 97% of them (65 requests) were addressed to the original Wiki.pentaho.com, 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (607 ms) belongs to the original domain Wiki.pentaho.com.
Page size can be reduced by 137.1 kB (80%)
171.4 kB
34.3 kB
In fact, the total size of Wiki.pentaho.com main page is 171.4 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. 15% of websites need less resources to load. HTML takes 154.3 kB which makes up the majority of the site volume.
Potential reduce by 137.1 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 137.1 kB or 89% of the original size.
Potential reduce by 34 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.
Number of requests can be reduced by 57 (86%)
66
9
The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wiki 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 14 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.
Community+Wiki+Home
425 ms
main-action.css
81 ms
batch.css
341 ms
com.adaptavist.confluence.themes.sitebuilder:nlstree-resources.css
81 ms
confluence.web.resources:view-comment.css
81 ms
confluence.macros.advanced:fancy-box.css
81 ms
com.atlassian.confluence.plugins.drag-and-drop:support.css
228 ms
combined.css
159 ms
batch.js
601 ms
com.adaptavist.confluence.themes.sitebuilder:ajs-compat-resources.js
157 ms
nlstree.js
303 ms
com.adaptavist.confluence.themes.sitebuilder:nlstree-resources.js
235 ms
com.adaptavist.confluence.themes.sitebuilder:pagetree-resources.js
234 ms
confluence.macros.advanced:fancy-box.js
306 ms
confluence.macros.advanced:thumbnail-images.js
310 ms
com.atlassian.confluence.plugins.fixedwidth-theme:fixedwidth-resources.js
313 ms
com.atlassian.confluence.plugins.drag-and-drop:support.js
424 ms
com.atlassian.confluence.plugins.drag-and-drop:drag-and-drop-for-view-content.js
381 ms
com.atlassian.confluence.plugins.doctheme:splitter.js
397 ms
legacy.confluence.web.resources:prototype.js
556 ms
skin-longhorn.css
386 ms
layout-resources.action
472 ms
layout-resources.action
464 ms
layout-resources.action
607 ms
site-2.5.css
503 ms
colors.css
497 ms
custom.css
511 ms
hmenu-extended.css
81 ms
hmenu.css
89 ms
shadow.png
116 ms
global.logo
114 ms
white-TopL.gif
116 ms
white-TopR.gif
115 ms
white-BtmL.gif
113 ms
white-BtmR.gif
114 ms
children.action
141 ms
plusnb.gif
134 ms
plusb.gif
137 ms
blank.gif
137 ms
minusnb.gif
154 ms
minusb.gif
155 ms
folderopen.gif
212 ms
folder.gif
216 ms
leaf.gif
215 ms
root.gif
214 ms
lineang.gif
216 ms
lineints.gif
217 ms
line.gif
289 ms
nodrop.gif
290 ms
folder_closed.png
296 ms
folder.png
294 ms
view.png
293 ms
ga.js
35 ms
i18n.action
222 ms
__utm.gif
11 ms
lt.png
280 ms
rt.png
284 ms
l.png
286 ms
r.png
288 ms
lb.png
289 ms
rb.png
295 ms
b.png
356 ms
children.action
300 ms
document_plain.png
296 ms
home.png
295 ms
calendar.png
297 ms
batch.css
89 ms
wiki.pentaho.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
wiki.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
wiki.pentaho.com SEO score
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
N/A
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wiki.pentaho.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 Wiki.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.
wiki.pentaho.com
Open Graph description is not detected on the main page of Wiki 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: