Tools & Wizards About Us
whatsonsydney.com screenshot

Report Summary

  • 11

    Performance

    Renders faster than
    24% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

whatsonsydney.com

What's On Sydney - Sydney's number one guide to What's on

Page Load Speed

5.7 sec in total

First Response

632 ms

Resources Loaded

4.7 sec

Page Rendered

321 ms

whatsonsydney.com screenshot

About Website

Visit whatsonsydney.com now to see the best up-to-date Whatson Sydney content for Australia and also check out these interesting facts you probably never knew about whatsonsydney.com

What's on Sydney gives you all the latest events in Sydney and New South Wales. Find out what's on today or what's on this weekend.

Visit whatsonsydney.com

Key Findings

We analyzed Whatsonsydney.com page load time and found that the first response time was 632 ms and then it took 5.1 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

whatsonsydney.com performance score

11

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

38/100

10%

LCP (Largest Contentful Paint)

Value14.6 s

0/100

25%

SI (Speed Index)

Value10.1 s

9/100

10%

TBT (Total Blocking Time)

Value2,980 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.328

35/100

15%

TTI (Time to Interactive)

Value15.9 s

6/100

10%

Network Requests Diagram

whatsonsydney.com

632 ms

whatsonsydney.com

853 ms

www.whatsonsydney.com

1228 ms

css

214 ms

js

71 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 21% of them (9 requests) were addressed to the original Whatsonsydney.com, 17% (7 requests) were made to Tpc.googlesyndication.com and 14% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Whatsonsydney.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 135.0 kB (32%)

Content Size

428.3 kB

After Optimization

293.3 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Whatsonsydney.com main page is 428.3 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. 55% of websites need less resources to load. Javascripts take 221.5 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 111.1 kB

  • Original 127.8 kB
  • After minification 99.9 kB
  • After compression 16.7 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 27.9 kB, which is 22% 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 111.1 kB or 87% of the original size.

Image Optimization

-29%

Potential reduce by 23.1 kB

  • Original 79.0 kB
  • After minification 55.9 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. Obviously, Whatson Sydney needs image optimization as it can save up to 23.1 kB or 29% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 785 B

  • Original 221.5 kB
  • After minification 221.5 kB
  • After compression 220.7 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.

Requests Breakdown

Number of requests can be reduced by 16 (55%)

Requests Now

29

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

whatsonsydney.com

whatsonsydney.com

632 ms

whatsonsydney.com

whatsonsydney.com

853 ms

www.whatsonsydney.com

www.whatsonsydney.com

1228 ms

css

css

214 ms

js

js

71 ms

jqueryhome

jqueryhome

870 ms

lazyload.js

lazyload.js

32 ms

adsbygoogle.js

adsbygoogle.js

124 ms

logo.png

logo.png

555 ms

bg_direction_nav.png

bg_direction_nav.png

668 ms

ajax-loader-newsdesk.gif

ajax-loader-newsdesk.gif

694 ms

gpt.js

gpt.js

154 ms

ga.js

ga.js

74 ms

-g5pDUSRgvxvOl5u-a_WHw.woff

-g5pDUSRgvxvOl5u-a_WHw.woff

95 ms

HqHm7BVC_nzzTui2lzQTDT8E0i7KZn-EPnyo3HZu7kw.woff

HqHm7BVC_nzzTui2lzQTDT8E0i7KZn-EPnyo3HZu7kw.woff

96 ms

bH7276GfdCjMjApa_dkG6T8E0i7KZn-EPnyo3HZu7kw.woff

bH7276GfdCjMjApa_dkG6T8E0i7KZn-EPnyo3HZu7kw.woff

128 ms

sDRi4fY9bOiJUbgq53yZCfesZW2xOQ-xsNqO47m55DA.woff

sDRi4fY9bOiJUbgq53yZCfesZW2xOQ-xsNqO47m55DA.woff

128 ms

QABk9IxT-LFTJ_dQzv7xpIbN6UDyHWBl620a-IRfuBk.woff

QABk9IxT-LFTJ_dQzv7xpIbN6UDyHWBl620a-IRfuBk.woff

200 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1225 ms

__utm.gif

__utm.gif

36 ms

collect

collect

12 ms

pubads_impl.js

pubads_impl.js

43 ms

2477004

2477004

55 ms

ads

ads

732 ms

container.html

container.html

34 ms

load_preloaded_resource.js

load_preloaded_resource.js

133 ms

icon.png

icon.png

39 ms

abg_lite.js

abg_lite.js

153 ms

s

s

128 ms

window_focus.js

window_focus.js

152 ms

qs_click_protection.js

qs_click_protection.js

137 ms

bbae3fd3506d8d9338f85d10ea9db8af.js

bbae3fd3506d8d9338f85d10ea9db8af.js

151 ms

icon.png

icon.png

73 ms

one_click_handler_one_afma.js

one_click_handler_one_afma.js

99 ms

221875747520804676

221875747520804676

179 ms

6359202143502294241

6359202143502294241

77 ms

3b0c1a1c8750041eb27603629860e89a.js

3b0c1a1c8750041eb27603629860e89a.js

30 ms

f11bfab4e3c942216447974439595ef6.js

f11bfab4e3c942216447974439595ef6.js

37 ms

css

css

119 ms

icon.png

icon.png

100 ms

BH9AwhYWkb0_O6DbNzExeTLtwTfGbFpL2lxnYW5uNe0.js

BH9AwhYWkb0_O6DbNzExeTLtwTfGbFpL2lxnYW5uNe0.js

23 ms

font

font

6 ms

Accessibility Review

whatsonsydney.com accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

whatsonsydney.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

whatsonsydney.com SEO score

84

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

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

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 Whatsonsydney.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 Whatsonsydney.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.

Social Sharing Optimization

whatsonsydney.com

Open Graph description is not detected on the main page of Whatson Sydney. 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: