Tools & Wizards About Us
wiseberry.com.au screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 82

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

wiseberry.com.au

Wiseberry Real Estate | Buy, Rent, Sell, Manage

Page Load Speed

5.8 sec in total

First Response

453 ms

Resources Loaded

5 sec

Page Rendered

312 ms

wiseberry.com.au screenshot

About Website

Click here to check amazing Wiseberry content for Australia. Otherwise, check out these important facts you probably never knew about wiseberry.com.au

Wiseberry Real Estate is a boutique real estate network offering premium buying, selling, renting, and property management services across NSW and Gold Coast Australia.

Visit wiseberry.com.au

Key Findings

We analyzed Wiseberry.com.au page load time and found that the first response time was 453 ms and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

wiseberry.com.au performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value15.5 s

0/100

25%

SI (Speed Index)

Value9.5 s

12/100

10%

TBT (Total Blocking Time)

Value2,110 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

wiseberry.com.au

453 ms

wiseberry.com.au

1138 ms

a402b81b84d45db3.css

442 ms

9fedf6aabaa2a4f1.css

627 ms

dba9ff2be4bcd569.css

647 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 98% of them (61 requests) were addressed to the original Wiseberry.com.au, 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Wiseberry.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.7 kB (7%)

Content Size

1.6 MB

After Optimization

1.5 MB

  • HTML
  • Images

In fact, the total size of Wiseberry.com.au main page is 1.6 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. 35% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 111.4 kB

  • Original 133.4 kB
  • After minification 133.2 kB
  • After compression 21.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 111.4 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 1.2 kB

  • Original 1.5 MB
  • After minification 1.5 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. Wiseberry images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 42 (70%)

Requests Now

60

After Optimization

18

  • Images
  • JavaScript
  • CSS

The browser has sent 60 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wiseberry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 38 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wiseberry.com.au

wiseberry.com.au

453 ms

wiseberry.com.au

wiseberry.com.au

1138 ms

a402b81b84d45db3.css

a402b81b84d45db3.css

442 ms

9fedf6aabaa2a4f1.css

9fedf6aabaa2a4f1.css

627 ms

dba9ff2be4bcd569.css

dba9ff2be4bcd569.css

647 ms

786eda8c4b5d7c2c.css

786eda8c4b5d7c2c.css

631 ms

9392bf3d6f367dea.css

9392bf3d6f367dea.css

636 ms

fd9d1056-8f33c521fc203703.js

fd9d1056-8f33c521fc203703.js

1062 ms

7023-c23e7ede7d6ec73d.js

7023-c23e7ede7d6ec73d.js

677 ms

main-app-55bbd77d79f9187f.js

main-app-55bbd77d79f9187f.js

828 ms

160b575a-e00647025013e2c4.js

160b575a-e00647025013e2c4.js

832 ms

6516-6149cfeaee352ef5.js

6516-6149cfeaee352ef5.js

1042 ms

231-4808bb429da46a12.js

231-4808bb429da46a12.js

851 ms

8173-ef7d163ead40ad1b.js

8173-ef7d163ead40ad1b.js

889 ms

9445-db0c8a845cc4f6bc.js

9445-db0c8a845cc4f6bc.js

1037 ms

8702-4df6919cea01adfc.js

8702-4df6919cea01adfc.js

1239 ms

5512-38892f2f2b06b7b5.js

5512-38892f2f2b06b7b5.js

1057 ms

8217-2424529304f52cf1.js

8217-2424529304f52cf1.js

1101 ms

9330-7ecfc89876f3d748.js

9330-7ecfc89876f3d748.js

1445 ms

9828-63868ea23654a0fb.js

9828-63868ea23654a0fb.js

1247 ms

5261-0b1e42e1837a3370.js

5261-0b1e42e1837a3370.js

1261 ms

3304-d760eed43d0dfad5.js

3304-d760eed43d0dfad5.js

1262 ms

4264-3cd40b73b9ffd65f.js

4264-3cd40b73b9ffd65f.js

1305 ms

1888-398dc8b7e98e6f27.js

1888-398dc8b7e98e6f27.js

1447 ms

6924-0b0f1755df06c9c9.js

6924-0b0f1755df06c9c9.js

1453 ms

83-a6903fcbae141216.js

83-a6903fcbae141216.js

1674 ms

2299-3e102eff37f15dea.js

2299-3e102eff37f15dea.js

1490 ms

7440-9ab21eb2acfb6f62.js

7440-9ab21eb2acfb6f62.js

1513 ms

6842-2f607b33d79c3a4a.js

6842-2f607b33d79c3a4a.js

1646 ms

8025-90cdd6ac56686de1.js

8025-90cdd6ac56686de1.js

1649 ms

layout-e45875f8a51900a5.js

layout-e45875f8a51900a5.js

1657 ms

7667-7a3ef96bcf088313.js

7667-7a3ef96bcf088313.js

1702 ms

template-8c511a9719914b31.js

template-8c511a9719914b31.js

1714 ms

2134-7853b656199e52e2.js

2134-7853b656199e52e2.js

1850 ms

682-9e7862436bd8165d.js

682-9e7862436bd8165d.js

1851 ms

page-4ce9e3cd58cf4655.js

page-4ce9e3cd58cf4655.js

1859 ms

a4634e51-628c9225afdc347d.js

a4634e51-628c9225afdc347d.js

2277 ms

1140-75c2d6524d4340f0.js

1140-75c2d6524d4340f0.js

1712 ms

485-5a5adec175ba4ec0.js

485-5a5adec175ba4ec0.js

1480 ms

5380-c917ac0ecf46fbb4.js

5380-c917ac0ecf46fbb4.js

1644 ms

8315-5453adba87433ff6.js

8315-5453adba87433ff6.js

1434 ms

991-4d970bae6eb51cd8.js

991-4d970bae6eb51cd8.js

1433 ms

css2

css2

41 ms

layout-11a81a19190f1996.js

layout-11a81a19190f1996.js

1468 ms

polyfills-78c92fac7aa8fdd8.js

polyfills-78c92fac7aa8fdd8.js

1458 ms

webpack-8ae7892a8534244c.js

webpack-8ae7892a8534244c.js

1438 ms

image

image

205 ms

image

image

413 ms

image

image

608 ms

image

image

304 ms

image

image

307 ms

image

image

522 ms

image

image

1015 ms

image

image

1122 ms

image

image

1131 ms

image

image

1064 ms

image

image

792 ms

image

image

1334 ms

image

image

1483 ms

image

image

1485 ms

image

image

1485 ms

image

image

1486 ms

Accessibility Review

wiseberry.com.au accessibility score

82

Accessibility Issues

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

High

Buttons do not have an accessible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

wiseberry.com.au best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

wiseberry.com.au SEO score

89

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Wiseberry.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 Wiseberry.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.

Social Sharing Optimization

wiseberry.com.au

Open Graph data is detected on the main page of Wiseberry. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: