3.1 sec in total
12 ms
1.9 sec
1.1 sec
Welcome to weka.pentaho.org homepage info - get ready to check Weka Pentaho best content for Russia right away, or after learning these important things about weka.pentaho.org
The site home page
Visit weka.pentaho.orgWe analyzed Weka.pentaho.org page load time and found that the first response time was 12 ms and then it took 3.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.
weka.pentaho.org performance score
name
value
score
weighting
Value15.4 s
0/100
10%
Value30.0 s
0/100
25%
Value15.4 s
0/100
10%
Value910 ms
31/100
30%
Value0
100/100
15%
Value20.2 s
2/100
10%
12 ms
41 ms
55 ms
31 ms
246 ms
Our browser made a total of 96 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Weka.pentaho.org, 17% (16 requests) were made to D2x5ku95bkycr3.cloudfront.net and 15% (14 requests) were made to Higherlogicdownload.s3.amazonaws.com. The less responsive or slowest element that took the longest time to load (941 ms) relates to the external source Higherlogicdownload.s3.amazonaws.com.
Page size can be reduced by 1.8 MB (28%)
6.4 MB
4.6 MB
In fact, the total size of Weka.pentaho.org main page is 6.4 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.9 MB which makes up the majority of the site volume.
Potential reduce by 142.3 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 28.3 kB, which is 14% 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 142.3 kB or 69% of the original size.
Potential reduce by 1.3 MB
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, Weka Pentaho needs image optimization as it can save up to 1.3 MB or 27% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 102.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 102.0 kB or 13% of the original size.
Potential reduce by 179.2 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. Weka.pentaho.org needs all CSS files to be minified and compressed as it can save up to 179.2 kB or 42% of the original size.
Number of requests can be reduced by 50 (66%)
76
26
The browser has sent 76 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Weka 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 33 to 1 for JavaScripts and from 19 to 1 for CSS and as a result speed up the page load time.
weka.pentaho.org
12 ms
DOC-1009857
41 ms
doc-1009857
55 ms
home
31 ms
home
246 ms
all.min.css
115 ms
prism.min.css
114 ms
bootstrap.min.css
104 ms
Desktop_bundle.min.132ecbb6b690203f49239d72314bae5d5bd3be62.hash.css
134 ms
jquery-ui.css
163 ms
css
160 ms
css
185 ms
css
208 ms
css
208 ms
css
207 ms
css
195 ms
css
208 ms
fontawesome-all.css
195 ms
slick-theme.css
159 ms
slick.css
175 ms
33
144 ms
iiw3mlf.css
159 ms
promise-fetch-polyfill.js
111 ms
system.min.js
152 ms
jQuery.1.10.2-patched-2022-12-05.js
157 ms
jQuery-migrate-1.2.1-patched-2023-04-03.js
164 ms
jQuery-ui.1.10.1-patched-2022-08-16.js
173 ms
bootstrap.min.js
109 ms
easyXDM.Min.js
79 ms
react.production.16.10.1.min.js
152 ms
react-dom.production.16.10.1.min.js
156 ms
prism.min.js
162 ms
prism-autoloader.min.js
170 ms
Desktop_bundle.min.42b988b9de1aa592b42b27e5d33ff306e7f50f26.hash.js
166 ms
d67f56a0.js
167 ms
slick.min.js
186 ms
CommunitySiteTheme1_638156997126644861.js
199 ms
parallax.min.js
202 ms
WebForms.js
159 ms
MicrosoftAjax.js
159 ms
MicrosoftAjaxWebForms.js
159 ms
ReactRootLegacy~hlReactRootLegacyRemote.bundle.c0c5ed4db81f121c24e8.hash.js
154 ms
ReactRoot~runtime~main.bundle.104cb44419e13797be13.hash.js
148 ms
ReactRoot~react-_yarn_cache_react-npm-18_2_0-1eae08fee2-88e38092da_zip_node_modules_react_index_js.bundle.fc5341e9cf64fffa77ef.hash.js
147 ms
ReactRoot~vendor-_yarn___virtual___react-dom-virtual-05f150c4a1_0_cache_react-dom-npm-18_2_0-dd675bca1c-eb9bcf.bundle.314b85227bb60497ccee.hash.js
153 ms
ReactRoot~vendor-_yarn___virtual___react-dom-virtual-05f150c4a1_0_cache_react-dom-npm-18_2_0-dd675bca1c-d944d6.bundle.4d5480f84c874d064ef9.hash.js
156 ms
ReactRoot~main.bundle.f332f2c01f63825e2088.hash.js
158 ms
js-for-FOUC.min.js
197 ms
background-images.js
187 ms
p.css
48 ms
bluebird.3.5.0.min.js
3 ms
fetch-polyfill.js
9 ms
woff.css
18 ms
gtm.js
765 ms
HV-Logo-White-RGB-Web.png
51 ms
0_200.png
48 ms
637848932362830000
50 ms
0_50.png
50 ms
loading.gif
50 ms
featureinsights.jpg
686 ms
16d2fceb1d04434ab61c822bf2f6ead1.png
941 ms
learn.png
845 ms
connect.png
846 ms
grow.png
845 ms
facebook-icon-new.svg
761 ms
twitter-icon-new.svg
755 ms
linkedin-icon-new.svg
841 ms
youtube-icon-new.svg
844 ms
instagram-icon-new.svg
890 ms
637716116907530000
68 ms
637848067846870000
68 ms
d
636 ms
d
705 ms
d
708 ms
d
687 ms
d
772 ms
d
772 ms
fa-regular-400.woff
772 ms
fa-regular-400.ttf
823 ms
fa-light-300.woff
918 ms
fa-light-300.ttf
823 ms
fa-solid-900.woff
870 ms
fa-solid-900.ttf
822 ms
glyphicons-halflings-regular.woff
688 ms
flash.png
897 ms
blank.htm
544 ms
ajax-loader.gif
488 ms
undefined
298 ms
communityhomehero.jpg
393 ms
383 ms
vfYHSPwBd1gm5AA==
2 ms
analytics.js
102 ms
home
301 ms
easyXDM.min.js
48 ms
collect
13 ms
js
34 ms
weka.pentaho.org 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
ARIA input fields do not have accessible names
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
<frame> or <iframe> elements do not have a title
Image elements do not have [alt] attributes
Links do not have a discernible name
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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>).
weka.pentaho.org 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
Issues were logged in the Issues panel in Chrome Devtools
weka.pentaho.org 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
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
Tap targets are not sized appropriately
EN
EN
N/A
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Weka.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 Weka.pentaho.org 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.
weka.pentaho.org
Open Graph description is not detected on the main page of Weka 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: