11.9 sec in total
1.7 sec
10 sec
203 ms
Click here to check amazing Profloor content. Otherwise, check out these important facts you probably never knew about profloor.com.au
Overview Gallery Technical Data Quick Quote Pro-Floor® EF Introduction Pro-Floor® EF is the ultimate event flooring
Visit profloor.com.auWe analyzed Profloor.com.au page load time and found that the first response time was 1.7 sec and then it took 10.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
profloor.com.au performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value18.9 s
0/100
25%
Value19.6 s
0/100
10%
Value1,690 ms
11/100
30%
Value0.054
98/100
15%
Value18.8 s
3/100
10%
1662 ms
579 ms
1016 ms
612 ms
653 ms
Our browser made a total of 163 requests to load all elements on the main page. We found that 81% of them (132 requests) were addressed to the original Profloor.com.au, 12% (20 requests) were made to Fonts.gstatic.com and 3% (5 requests) were made to Use.fontawesome.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Profloor.com.au.
Page size can be reduced by 2.3 MB (46%)
5.0 MB
2.7 MB
In fact, the total size of Profloor.com.au main page is 5.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.8 MB which makes up the majority of the site volume.
Potential reduce by 71.9 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 71.9 kB or 82% of the original size.
Potential reduce by 6.5 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. Profloor images are well optimized though.
Potential reduce by 1.1 MB
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 1.1 MB or 63% of the original size.
Potential reduce by 1.1 MB
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. Profloor.com.au needs all CSS files to be minified and compressed as it can save up to 1.1 MB or 85% of the original size.
Number of requests can be reduced by 115 (85%)
135
20
The browser has sent 135 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Profloor. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 93 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
www.profloor.com.au
1662 ms
wp-emoji-release.min.js
579 ms
dashicons.min.css
1016 ms
jquery-ui-dialog.min.css
612 ms
sbi-styles.min.css
653 ms
layerslider.css
811 ms
css
32 ms
style.min.css
815 ms
styles.css
617 ms
style.css
1252 ms
prettyPhoto.min.css
1027 ms
style.css
859 ms
font-awesome.min.css
1015 ms
elegant-icons.min.css
1020 ms
mediaelementplayer-legacy.min.css
1049 ms
wp-mediaelement.min.css
1065 ms
stylesheet.min.css
1825 ms
responsive.min.css
1225 ms
style_dynamic_responsive.css
1233 ms
style_dynamic.css
1257 ms
js_composer.min.css
2092 ms
css
34 ms
all.css
38 ms
style.css
1430 ms
v4-shims.css
56 ms
jquery.min.js
1846 ms
jquery-migrate.min.js
1456 ms
greensock.js
1859 ms
layerslider.kreaturamedia.jquery.js
1836 ms
layerslider.transitions.js
1661 ms
jquery.prettyPhoto.min.js
1866 ms
underscore.min.js
2028 ms
infinite-scroll.pkgd.min.js
2041 ms
front.js
2052 ms
jPushMenu.js
1868 ms
profloor.js
1876 ms
core.min.js
2038 ms
mouse.min.js
2051 ms
resizable.min.js
2065 ms
draggable.min.js
2073 ms
element.js
51 ms
recaptcha_ajax.js
24 ms
api.js
43 ms
controlgroup.min.js
2078 ms
checkboxradio.min.js
1896 ms
button.min.js
2003 ms
dialog.min.js
1841 ms
wpdialog.min.js
1820 ms
index.js
1670 ms
index.js
1669 ms
scripts.js
1669 ms
doubletaptogo.js
1791 ms
modernizr.min.js
1649 ms
jquery.appear.js
1659 ms
hoverIntent.min.js
1657 ms
droppable.min.js
1641 ms
selectable.min.js
1655 ms
sortable.min.js
1629 ms
accordion.min.js
1638 ms
menu.min.js
1639 ms
regenerator-runtime.min.js
1632 ms
style.css
1687 ms
wp-polyfill.min.js
1471 ms
dom-ready.min.js
1397 ms
hooks.min.js
1238 ms
i18n.min.js
1310 ms
a11y.min.js
1303 ms
autocomplete.min.js
1290 ms
datepicker.min.js
1425 ms
effect.min.js
1283 ms
effect-blind.min.js
1292 ms
effect-bounce.min.js
1282 ms
effect-clip.min.js
1294 ms
effect-drop.min.js
1409 ms
effect-explode.min.js
1394 ms
effect-fade.min.js
1307 ms
effect-fold.min.js
1294 ms
effect-highlight.min.js
1288 ms
effect-pulsate.min.js
1417 ms
effect-size.min.js
1429 ms
effect-scale.min.js
1451 ms
effect-shake.min.js
1309 ms
effect-slide.min.js
1298 ms
effect-transfer.min.js
1289 ms
progressbar.min.js
1417 ms
slider.min.js
1430 ms
spinner.min.js
1447 ms
tabs.min.js
1311 ms
tooltip.min.js
1296 ms
absoluteCounter.min.js
1288 ms
jquery.easy-pie-chart.js
1419 ms
jquery.mixitup.min.js
1431 ms
jquery.nicescroll.min.js
1441 ms
jquery.fitvids.js
1312 ms
jquery.flexslider-min.js
1301 ms
mediaelement-and-player.min.js
1286 ms
mediaelement-migrate.min.js
1415 ms
wp-mediaelement.min.js
1395 ms
infiniteScroll.min.js
1308 ms
jquery.waitforimages.js
1293 ms
jquery.form.min.js
1230 ms
waypoints.min.js
1234 ms
jplayer.min.js
1362 ms
bootstrap.carousel.js
1344 ms
S6uyw4BMUTPHjx4wWw.ttf
149 ms
S6u9w4BMUTPHh7USSwiPHA.ttf
169 ms
S6u8w4BMUTPHh30AXC-v.ttf
170 ms
S6u9w4BMUTPHh6UVSwiPHA.ttf
170 ms
S6u9w4BMUTPHh50XSwiPHA.ttf
169 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf
170 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf
169 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf
174 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf
172 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf
171 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf
173 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf
173 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf
173 ms
1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf
174 ms
fa-solid-900.woff
104 ms
fa-regular-400.woff
121 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf
87 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0B4gaVc.ttf
89 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf
89 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf
88 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf
88 ms
memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf
89 ms
fa-brands-400.woff
58 ms
skrollr.js
1279 ms
Chart.min.js
1455 ms
jquery.easing.1.3.js
1246 ms
jquery.carouFredSel-6.2.1.js
1255 ms
lemmon-slider.js
1357 ms
jquery.mousewheel.min.js
1249 ms
jquery.touchSwipe.min.js
1282 ms
isotope.pkgd.min.js
1248 ms
default_dynamic.js
1256 ms
default.min.js
1374 ms
comment-reply.min.js
1250 ms
js_composer_front.min.js
1274 ms
qode-like.js
1238 ms
index.js
1247 ms
ElegantIcons.woff
1306 ms
prolfoor-logo-2015.png
1374 ms
profloor-slide5.jpg
1253 ms
left.png
1277 ms
right.png
1234 ms
profloor-slide2.jpg
1460 ms
portable-profloor-flooring.jpg
1308 ms
profloor-slide6.jpg
1576 ms
profloor-slide1.jpg
1258 ms
profloor-slide4.jpg
1884 ms
event-flooring.jpg
1241 ms
grass-protection.jpg
1312 ms
access-roadway-systems.jpg
1396 ms
profloor-brochure-1.gif
1428 ms
profloor-footer-logo.png
1317 ms
recaptcha__en.js
79 ms
skin.css
677 ms
logo.png
689 ms
skin.png
208 ms
icon-muted-white.png
209 ms
icon-unmuted-white.png
209 ms
fontawesome-webfont.woff
214 ms
profloor.com.au 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.
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
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
profloor.com.au 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
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
profloor.com.au 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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Profloor.com.au 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 Profloor.com.au 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.
profloor.com.au
Open Graph data is detected on the main page of Profloor. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: