Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 78

    SEO

    Google-friendlier than
    39% of websites

plonk.net.au

Online Beer Store | Beer and wines Canberra | Plonk

Page Load Speed

6.7 sec in total

First Response

486 ms

Resources Loaded

5.7 sec

Page Rendered

515 ms

plonk.net.au screenshot

About Website

Welcome to plonk.net.au homepage info - get ready to check Plonk best content right away, or after learning these important things about plonk.net.au

Online Beer Store, Beer and wines canberra ,Plonk has grown to one of Canberra’s most recognised spots for Aussie craft beers.

Visit plonk.net.au

Key Findings

We analyzed Plonk.net.au page load time and found that the first response time was 486 ms and then it took 6.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

plonk.net.au performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value36.3 s

0/100

25%

SI (Speed Index)

Value27.5 s

0/100

10%

TBT (Total Blocking Time)

Value11,850 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.018

100/100

15%

TTI (Time to Interactive)

Value39.0 s

0/100

10%

Network Requests Diagram

plonk.net.au

486 ms

plonk.net.au

1123 ms

js

111 ms

diffuser.js

56 ms

fbevents.js

55 ms

Our browser made a total of 250 requests to load all elements on the main page. We found that 87% of them (218 requests) were addressed to the original Plonk.net.au, 4% (9 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Plonk.net.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (17%)

Content Size

6.0 MB

After Optimization

5.0 MB

In fact, the total size of Plonk.net.au main page is 6.0 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. Only a small number of websites need less resources to load. Images take 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-92%

Potential reduce by 760.9 kB

  • Original 824.6 kB
  • After minification 776.8 kB
  • After compression 63.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. 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 760.9 kB or 92% of the original size.

Image Optimization

-7%

Potential reduce by 255.9 kB

  • Original 3.6 MB
  • After minification 3.3 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. Plonk images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 15.9 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 1.3 MB

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.

CSS Optimization

-3%

Potential reduce by 11.0 kB

  • Original 333.6 kB
  • After minification 333.0 kB
  • After compression 322.7 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. Plonk.net.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 189 (81%)

Requests Now

232

After Optimization

43

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

Accessibility Review

plonk.net.au accessibility score

81

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA input fields do not have accessible names

High

ARIA IDs are not unique

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.

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

Low

No form fields have multiple labels

High

Links do not have a discernible name

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

plonk.net.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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

plonk.net.au SEO score

78

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

High

robots.txt is not valid

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 Plonk.net.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 Plonk.net.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

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