2.4 sec in total
23 ms
2.1 sec
362 ms
Click here to check amazing Play content for Australia. Otherwise, check out these important facts you probably never knew about play.afl
Visit play.aflWe analyzed Play.afl page load time and found that the first response time was 23 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.
play.afl performance score
name
value
score
weighting
Value5.8 s
4/100
10%
Value13.8 s
0/100
25%
Value12.9 s
2/100
10%
Value1,630 ms
12/100
30%
Value1.044
2/100
15%
Value24.0 s
1/100
10%
23 ms
11 ms
55 ms
344 ms
341 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 45% of them (14 requests) were addressed to the original Play.afl, 19% (6 requests) were made to Fonts.gstatic.com and 13% (4 requests) were made to Player.vimeo.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Play.afl.
Page size can be reduced by 282.5 kB (16%)
1.8 MB
1.5 MB
In fact, the total size of Play.afl main page is 1.8 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. Javascripts take 889.2 kB which makes up the majority of the site volume.
Potential reduce by 93.2 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 15.5 kB, which is 15% 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 93.2 kB or 91% of the original size.
Potential reduce by 187.6 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, Play needs image optimization as it can save up to 187.6 kB or 24% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 1.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.
Potential reduce by 51 B
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. Play.afl has all CSS files already compressed.
Number of requests can be reduced by 9 (45%)
20
11
The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Play. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 7 to 1 for JavaScripts and from 4 to 1 for CSS and as a result speed up the page load time.
play.afl
23 ms
css_JQyZ9StD4-4I5jikYtL8icbvn1b-f6xMTWUzpXDhKlc.css
11 ms
css_fYoPeCHwYIIgZqcdRqAeI-oW2Y66QkIn59ZlukRMK2E.css
55 ms
27944750178.js
344 ms
js_HmJ6eCZuonCnANpH0xLFwytcUtNxyIx5v3fGu4C9SNY.js
341 ms
svgxuse.min.js
343 ms
js_qjYGblQ8KPxVLFIxL1jZ8HVlCxVMCa5W0svh75zrj38.js
342 ms
css2
287 ms
css2
307 ms
geo4.js
113 ms
gtm.js
159 ms
icons.svg
84 ms
879639469
254 ms
879639433
273 ms
879639459
305 ms
879639446
277 ms
AFL_PLAY_Logo_vertical.svg
268 ms
Australia%20Map%20Working%20Files_2.png
1533 ms
the_slice_0.jpg
294 ms
Socials.jpg
291 ms
PLAY-Logo_0.png
285 ms
AFL-Logo_play_0.png
301 ms
AFLW-Logo-Play.png
481 ms
a20932740777.html
60 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuLyfMZg.ttf
44 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuI6fMZg.ttf
52 ms
UcCO3FwrK3iLTeHuS_nVMrMxCp50SjIw2boKoduKmMEVuFuYMZg.ttf
68 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1xZogUE.ttf
67 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs18NvgUE.ttf
62 ms
TK3_WkUHHAIjg75cFRf3bXL8LICs1_FvgUE.ttf
67 ms
api.js
8 ms
play.afl accessibility score
play.afl 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
Browser errors were logged to the console
Missing source maps for large first-party JavaScript
play.afl SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
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 Play.afl 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 Play.afl 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.
play.afl
Open Graph description is not detected on the main page of Play. 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: