8 sec in total
427 ms
7.2 sec
341 ms
Visit pre.com.au now to see the best up-to-date Pre content and also check out these interesting facts you probably never knew about pre.com.au
Visit pre.com.auWe analyzed Pre.com.au page load time and found that the first response time was 427 ms and then it took 7.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.
pre.com.au performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value16.4 s
0/100
25%
Value15.4 s
0/100
10%
Value1,230 ms
20/100
30%
Value1.192
1/100
15%
Value24.1 s
0/100
10%
427 ms
1009 ms
104 ms
84 ms
1256 ms
Our browser made a total of 106 requests to load all elements on the main page. We found that 47% of them (50 requests) were addressed to the original Pre.com.au, 13% (14 requests) were made to A.tile.openstreetmap.org and 9% (10 requests) were made to Au-crm.cdns.rexsoftware.com. The less responsive or slowest element that took the longest time to load (4 sec) relates to the external source Au-crm.cdns.rexsoftware.com.
Page size can be reduced by 369.5 kB (6%)
6.7 MB
6.3 MB
In fact, the total size of Pre.com.au main page is 6.7 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 6.0 MB which makes up the majority of the site volume.
Potential reduce by 78.4 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 78.4 kB or 81% of the original size.
Potential reduce by 242.2 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. Pre images are well optimized though.
Potential reduce by 43.4 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. This website has mostly compressed JavaScripts.
Potential reduce by 5.6 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. Pre.com.au has all CSS files already compressed.
Number of requests can be reduced by 61 (63%)
97
36
The browser has sent 97 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pre. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 46 to 1 for JavaScripts and from 12 to 1 for CSS and as a result speed up the page load time.
pre.com.au
427 ms
pre.com.au
1009 ms
gtm.js
104 ms
analytics.min.js
84 ms
analytics-plugin-warehouse.min.js
1256 ms
royalslider.css
800 ms
chosen.min.css
824 ms
select2.css
828 ms
jquery.nouislider.css
826 ms
slick.min.css
84 ms
style.css
1218 ms
icons.css
826 ms
leaflet.css
82 ms
MarkerCluster.css
78 ms
style.css
995 ms
jquery.lazyloadxt.spinner.css
1018 ms
a3_lazy_load.min.css
1021 ms
bugsnag.js
1217 ms
jquery.js
1220 ms
slick.min.js
93 ms
jquery.autoellipsis-1.0.10.min.js
1190 ms
easing.js
1212 ms
webfont.js
66 ms
jquery-migrate.min.js
1215 ms
core.min.js
1461 ms
datepicker.min.js
1498 ms
underscore.min.js
1498 ms
es5-shim.min.js
93 ms
es5-sham.min.js
95 ms
bootstrap.min.js
1497 ms
masonry.js
1700 ms
jquery.royalslider.min.js
1497 ms
chosen.jquery.min.js
1712 ms
jquery.nouislider.min.js
1714 ms
jquery.stellar.min.js
1700 ms
jquery.colorbox-min.js
1710 ms
history.js
1710 ms
jquery.smartmenus.min.js
1933 ms
placeholders.jquery.min.js
1933 ms
picturefill.js
1933 ms
prototype_price_format_2.min.js
1932 ms
select2.js
1932 ms
leaflet.js
73 ms
leaflet.markercluster.js
74 ms
polyfill.js
2096 ms
ajax.js
2141 ms
globals.js
2140 ms
modules.js
2294 ms
scripts.js
2339 ms
theme.js
2142 ms
analytics.min.js
12 ms
jquery.lazyloadxt.extra.min.js
1505 ms
jquery.lazyloadxt.srcset.min.js
1593 ms
jquery.lazyloadxt.extend.js
1590 ms
wp-emoji-release.min.js
1153 ms
bwz7yvt.js
185 ms
analytics.js
180 ms
40-RICHARDSON-WEB-50_9330-d1a9-89e4-9faf-d35e-b7b6-c326-99f0_20240130083317_800x600.jpg
1816 ms
11-COOLAWANYAH-LR-71_f374-e170-e695-9aa9-185e-3d89-30b8-3a5c_20230221055330_800x600.jpg
349 ms
transparent-background-1.png
1904 ms
homepage.jpg
2098 ms
6-Brolga-Meander.jpg
1316 ms
robwebsite.jpg
1906 ms
ROB-SLEATOR22-4.jpg
1905 ms
ROB-SLEATOR-0020.jpg
2878 ms
11-COOLAWANYAH-LR-71_f374-e170-e695-9aa9-185e-3d89-30b8-3a5c_20230221055330.jpg
338 ms
34GREGORY-WEB-1875_f471-0d0b-a70b-d629-8e9a-20ba-12b8-62ba_20231106010021_800x600.jpg
431 ms
IMG_8629_42cc-b499-ea09-7a34-d2da-d32c-1f96-a065_20231009073654_800x600.jpg
2009 ms
86-MUJIRA-WEB-9765_01ee-a2d7-7c3d-3395-5dec-a88b-0b10-b0a7_20231011114550_800x600.jpg
2100 ms
map_20230503-1-_4368-f1e0-a940-9a7f-30d7-e45e-56dc-e600_20230808063305_800x600.jpg
1970 ms
40-RICHARDSON-WEB-50_9330-d1a9-89e4-9faf-d35e-b7b6-c326-99f0_20240130083317.jpg
2225 ms
34GREGORY-WEB-1875_f471-0d0b-a70b-d629-8e9a-20ba-12b8-62ba_20231106010021.jpg
2228 ms
IMG_8629_42cc-b499-ea09-7a34-d2da-d32c-1f96-a065_20231009073654.jpg
3757 ms
86-MUJIRA-WEB-9765_01ee-a2d7-7c3d-3395-5dec-a88b-0b10-b0a7_20231011114550.jpg
4024 ms
map_20230503-1-_4368-f1e0-a940-9a7f-30d7-e45e-56dc-e600_20230808063305.jpg
3888 ms
siteloft-template-icons.ttf
1431 ms
collect
179 ms
d
87 ms
d
117 ms
d
118 ms
d
119 ms
d
119 ms
collect
223 ms
js
93 ms
121 ms
fbevents.js
191 ms
js
122 ms
p.gif
117 ms
97 ms
ga-audiences
37 ms
collect
73 ms
9156.png
177 ms
select2.png
221 ms
9157.png
227 ms
9156.png
90 ms
9156.png
99 ms
9157.png
146 ms
9157.png
94 ms
9156.png
295 ms
9156.png
298 ms
9157.png
103 ms
9157.png
174 ms
9156.png
185 ms
9156.png
225 ms
9157.png
251 ms
9157.png
273 ms
pre.com.au 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
Document doesn't have a <title> element
<frame> or <iframe> elements do not have a title
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
pre.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
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
pre.com.au SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Document doesn't have a <title> element
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
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pre.com.au 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 Pre.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.
pre.com.au
Open Graph description is not detected on the main page of Pre. 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: