375 ms in total
107 ms
111 ms
157 ms
Click here to check amazing Demo Pentaho content for Australia. Otherwise, check out these important facts you probably never knew about demo.pentaho.com
Explore Pentaho Tutorials to learn about Pentaho Data Integration and take advantage of how-to videos, and documentation to get the most out of your download.
Visit demo.pentaho.comWe analyzed Demo.pentaho.com page load time and found that the first response time was 107 ms and then it took 268 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.
demo.pentaho.com performance score
name
value
score
weighting
Value5.1 s
8/100
10%
Value7.8 s
3/100
25%
Value12.0 s
4/100
10%
Value8,800 ms
0/100
30%
Value0.004
100/100
15%
Value29.0 s
0/100
10%
107 ms
Our browser made a total of 1 request to load all elements on the main page. We found that all of those requests were addressed to Demo.pentaho.com and no external sources were called. The less responsive or slowest element that took the longest time to load (107 ms) belongs to the original domain Demo.pentaho.com.
Page size can be reduced by 137 B (39%)
354 B
217 B
In fact, the total size of Demo.pentaho.com main page is 354 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 354 B which makes up the majority of the site volume.
Potential reduce by 137 B
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 59 B, which is 17% 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 137 B or 39% of the original size.
We found no issues to fix!
0
0
Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.
{{url}}
{{time}} ms
demo.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.
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
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
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
[lang] attributes do not have a valid value
demo.pentaho.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
demo.pentaho.com 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
Image elements do not have [alt] attributes
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
N/A
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Demo.pentaho.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Demo.pentaho.com main page’s claimed encoding is . Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
{{og_description}}
demo.pentaho.com
Open Graph description is not detected on the main page of Demo 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: