30.8 sec in total
1 sec
28.8 sec
981 ms
Welcome to watersedgecanberra.com.au homepage info - get ready to check Watersedge Canberra best content right away, or after learning these important things about watersedgecanberra.com.au
If you are looking for a modern Australian Fine dining restaurant Canberra, look no further. Waters Edge Canberra offers a unique dining experience for local residents and visitors. Waters edge comes ...
Visit watersedgecanberra.com.auWe analyzed Watersedgecanberra.com.au page load time and found that the first response time was 1 sec and then it took 29.7 sec 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. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.
watersedgecanberra.com.au performance score
name
value
score
weighting
Value7.0 s
1/100
10%
Value7.3 s
5/100
25%
Value15.8 s
0/100
10%
Value1,130 ms
22/100
30%
Value0.112
87/100
15%
Value16.3 s
5/100
10%
1033 ms
4270 ms
79 ms
514 ms
1004 ms
Our browser made a total of 102 requests to load all elements on the main page. We found that 68% of them (69 requests) were addressed to the original Watersedgecanberra.com.au, 8% (8 requests) were made to Lh3.googleusercontent.com and 6% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.2 sec) belongs to the original domain Watersedgecanberra.com.au.
Page size can be reduced by 174.2 kB (9%)
1.9 MB
1.7 MB
In fact, the total size of Watersedgecanberra.com.au main page is 1.9 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. 55% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 146.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. 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 146.8 kB or 83% of the original size.
Potential reduce by 20.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. Watersedge Canberra images are well optimized though.
Potential reduce by 4.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. This website has mostly compressed JavaScripts.
Potential reduce by 3.0 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. Watersedgecanberra.com.au has all CSS files already compressed.
Number of requests can be reduced by 63 (70%)
90
27
The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Watersedge Canberra. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 42 to 1 for JavaScripts and from 23 to 1 for CSS and as a result speed up the page load time.
watersedgecanberra.com.au
1033 ms
watersedgecanberra.com.au
4270 ms
js
79 ms
cookieblocker.min.css
514 ms
jquery.mCustomScrollbar.min.css
1004 ms
header-footer-elementor.css
831 ms
elementor-icons.min.css
1083 ms
frontend-lite.min.css
1421 ms
swiper.min.css
1459 ms
frontend-lite.min.css
1504 ms
all.min.css
1514 ms
v4-shims.min.css
1441 ms
fluent-forms-elementor-widget.css
1333 ms
frontend.css
1576 ms
style.css
1836 ms
style.css
3217 ms
style-main-new.min.css
1963 ms
css
44 ms
css
55 ms
mailin-front.css
3209 ms
css
59 ms
fontawesome.min.css
2032 ms
brands.min.css
1819 ms
timeme.min.js
2060 ms
burst.min.js
2277 ms
frontend-gtag.min.js
2476 ms
jquery.min.js
2550 ms
jquery-migrate.min.js
2317 ms
v4-shims.min.js
2760 ms
jquery-3.6.0.min.js
32 ms
script.js
2566 ms
mailin-front.js
2959 ms
trustindex-google-widget.css
3061 ms
fluent-forms-public.css
2828 ms
fluentform-public-default.css
3300 ms
jquery.mCustomScrollbar.concat.min.js
3353 ms
custom-scrollbar-enabler.min.js
3429 ms
frontend.js
5426 ms
comment-reply.min.js
3709 ms
complianz.min.js
4746 ms
loader.js
30 ms
api.js
46 ms
form-submission.js
3731 ms
frontend.js
3596 ms
js
80 ms
webpack-pro.runtime.min.js
3898 ms
js
49 ms
analytics.js
17 ms
collect
11 ms
webpack.runtime.min.js
3338 ms
frontend-modules.min.js
4399 ms
wp-polyfill-inert.min.js
3211 ms
regenerator-runtime.min.js
3016 ms
wp-polyfill.min.js
4553 ms
hooks.min.js
2915 ms
i18n.min.js
3248 ms
frontend.min.js
3130 ms
waypoints.min.js
3338 ms
core.min.js
3658 ms
frontend.min.js
4727 ms
elements-handlers.min.js
3268 ms
underscore.min.js
3497 ms
wp-util.min.js
3685 ms
frontend.min.js
3684 ms
gtm.js
98 ms
gtm.js
97 ms
ALm5wu38q1dtDd49K0WOMc1D_0qcdsK0aJWhoo2CDAXY=s120-c-c-rp-w64-h64-mo-br100
164 ms
ALm5wu1C2MgnbqKbcA0d0pERqWxko_INnw0cQsLPGfB2=s120-c-c-rp-w64-h64-mo-br100
240 ms
ACNPEu-3ijXD8B1alZfVFJL8ZrhgjjLZQgOtNrMUyLcWXQ=s120-c-c-rp-w64-h64-mo-br100
233 ms
ALm5wu1krgVZPhdVAC4CYwtwenO5WL6_0-t8va1ThMHj=s120-c-c-rp-w64-h64-mo-ba4-br100
187 ms
ACNPEu-JPIxUMvJT07BP_uki3i6UO_byZcxStdxNrRveMg=s120-c-c-rp-w64-h64-mo-ba5-br100
263 ms
ALm5wu0vD6elrL6vf-4E9L5CawvMkh_jEtxSXgvNj57X=s120-c-c-rp-w64-h64-mo-br100
172 ms
ACNPEu9CgXotdQGt2RfApxfitU3HJZEzNI1Sj6ELsVRwRA=s120-c-c-rp-w64-h64-mo-br100
287 ms
ALm5wu1H25Dr7DDiHKMS8wq8MIuiJ2qPzAfnkuz28S0m=s120-c-c-rp-w64-h64-mo-br100
185 ms
12-transparent-150x150.png
2580 ms
IMG_1576-scaled.jpg
11696 ms
winner-text-263x300.png
2880 ms
Gal2.jpg
5439 ms
Gal1.jpg
4816 ms
973A2775.jpg
20200 ms
Gal14-768x1024.jpg
3852 ms
Gal12-768x1024.jpg
11582 ms
Gal11-768x1024.jpg
4841 ms
Gal10-768x1024.jpg
5313 ms
Gal8-768x1024.jpg
5754 ms
f.svg
91 ms
h.svg
82 ms
icon.svg
82 ms
e.svg
83 ms
Gal5-768x1024.jpg
5998 ms
logo-dark.svg
5871 ms
KFOmCnqEu92Fr1Mu4mxM.woff
63 ms
KFOlCnqEu92Fr1MmEU9fBBc-.woff
79 ms
KFOlCnqEu92Fr1MmSU5fBBc-.woff
96 ms
KFOkCnqEu92Fr1MmgVxIIzQ.woff
108 ms
KFOlCnqEu92Fr1MmWUlfBBc-.woff
110 ms
KFOlCnqEu92Fr1MmYUtfBBc-.woff
109 ms
b51e8418-976c-4dac-967e-1d7f8f8769ea
66 ms
eicons.woff
6608 ms
api.min.js
33 ms
BalmoralStd.otf
6765 ms
fa-brands-400.woff
6182 ms
watersedgecanberra.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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
watersedgecanberra.com.au 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
watersedgecanberra.com.au SEO score
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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Watersedgecanberra.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 Watersedgecanberra.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.
watersedgecanberra.com.au
Open Graph data is detected on the main page of Watersedge Canberra. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: