3.7 sec in total
95 ms
3.5 sec
129 ms
Welcome to castex.com homepage info - get ready to check Castex best content right away, or after learning these important things about castex.com
Choose your location near you for floor cleaning machines & services based on your region, country or language preferences.
Visit castex.comWe analyzed Castex.com page load time and found that the first response time was 95 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.
castex.com performance score
name
value
score
weighting
Value11.0 s
0/100
10%
Value21.3 s
0/100
25%
Value11.0 s
6/100
10%
Value3,040 ms
2/100
30%
Value0.212
59/100
15%
Value20.2 s
2/100
10%
95 ms
193 ms
167 ms
43 ms
26 ms
Our browser made a total of 70 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Castex.com, 9% (6 requests) were made to Analytics.clickdimensions.com and 6% (4 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (959 ms) relates to the external source Tennantco.com.
Page size can be reduced by 292.9 kB (51%)
574.0 kB
281.2 kB
In fact, the total size of Castex.com main page is 574.0 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. 70% of websites need less resources to load. Javascripts take 413.7 kB which makes up the majority of the site volume.
Potential reduce by 105.8 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 25.3 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 105.8 kB or 87% of the original size.
Potential reduce by 398 B
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. Castex images are well optimized though.
Potential reduce by 157.5 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 157.5 kB or 38% of the original size.
Potential reduce by 29.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. Castex.com needs all CSS files to be minified and compressed as it can save up to 29.2 kB or 85% of the original size.
Number of requests can be reduced by 22 (61%)
36
14
The browser has sent 36 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Castex. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and as a result speed up the page load time.
www.tennantco.com
95 ms
www.tennantco.com
193 ms
localeselector.html
167 ms
ruxitagentjs_ICA23NVfqru_10281231207105659.js
43 ms
launch-8ff8a048f526.min.js
26 ms
jquery.min.cee8557e8779d371fe722bbcdd3b3eb7.js
93 ms
clientlib-dependencies.min.2316d58738370f2f908f027043c85723.js
36 ms
clientlib-base.min.a69c1b15aabf156afc51b6148260840b.css
141 ms
clientlib-blog.min.6d4ab4f5dd52d7e6ce51fb8c2177ac83.css
109 ms
KSxSb4Tw.js
23 ms
clientlib-base.min.57a860c5bc9831183353374c20fc7ef9.js
187 ms
clientlib-blog.min.ba32cffe5c41b525c54017fdea83247d.js
110 ms
clientlib-location.min.a3b0a7f4be5636e002191ba48801b7dc.js
115 ms
gtm.js
265 ms
analytics.js
47 ms
AppMeasurement.min.js
32 ms
AppMeasurement_Module_ActivityMap.min.js
37 ms
token.json
223 ms
js
187 ms
odb0k3nxee6a52bfvfb4cq.html
183 ms
js
103 ms
tennant-logo-150x70.png
87 ms
tc-facebook-icon.png
88 ms
tc-linkedin-icon.png
84 ms
tc-youtube-icon.png
84 ms
0.gif
85 ms
Open-Sans-regular.woff
85 ms
Open-Sans-300.woff
209 ms
Open-Sans-600.woff
86 ms
Open-Sans-700.woff
87 ms
fontello-1f8e61c9.woff
176 ms
open-sans-regular.woff
892 ms
open-sans-600.woff
447 ms
open-sans-700.woff
737 ms
cdform2.min.css
435 ms
cdform.jquery.js
492 ms
cdform.min.noanalytics.js
735 ms
xsscheck.js
734 ms
ts.js
87 ms
optout.js
87 ms
forms.js
117 ms
collect
107 ms
js
84 ms
bat.js
435 ms
insight.min.js
435 ms
fbevents.js
370 ms
collect
338 ms
open-sans-300.woff
795 ms
collect
606 ms
tsr.js
407 ms
collect
315 ms
js
102 ms
Open-Sans-600.ttf
221 ms
ga-audiences
60 ms
open-sans-600.ttf
375 ms
Open-Sans-700.ttf
36 ms
tsr.js
47 ms
ga-audiences
23 ms
open-sans-700.ttf
959 ms
Open-Sans-regular.ttf
22 ms
open-sans-regular.ttf
901 ms
Open-Sans-300.ttf
57 ms
Open-Sans-600.svg
87 ms
open-sans-600.svg
409 ms
Open-Sans-700.svg
130 ms
Open-Sans-regular.svg
107 ms
open-sans-700.svg
191 ms
open-sans-regular.svg
302 ms
printpage.css
48 ms
RCab1d8c40bf1c4c3ebe4874a2992bd9d1-source.min.js
13 ms
castex.com 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
<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
[id] attributes on active, focusable elements are not unique
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
castex.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Requests the geolocation permission on page load
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
castex.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
robots.txt is not valid
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 Castex.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 Castex.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.
castex.com
Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: