Tools & Wizards About Us
anzacs.net screenshot

Report Summary

  • 99

    Performance

    Renders faster than
    96% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

anzacs.net

IndexB.html

Page Load Speed

414 ms in total

First Response

120 ms

Resources Loaded

184 ms

Page Rendered

110 ms

anzacs.net screenshot

About Website

Click here to check amazing Anzacs content for Australia. Otherwise, check out these important facts you probably never knew about anzacs.net

The Anzac Tribute site, Stories of the Gallipoli Campaign, The controversy of who killed the Red Baron examined by experts, Audio poems from famous soldier/poets or WW1, audio from an eye witness to t...

Visit anzacs.net

Key Findings

We analyzed Anzacs.net page load time and found that the first response time was 120 ms and then it took 294 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

anzacs.net performance score

99

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value2.1 s

96/100

25%

SI (Speed Index)

Value1.0 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value1.0 s

100/100

10%

Network Requests Diagram

anzacs.net

120 ms

AnzacNEWbanner.gif

58 ms

Anzacs.gif

44 ms

RedButton2.gif

46 ms

RedBaron.gif

46 ms

Our browser made a total of 12 requests to load all elements on the main page. We found that 92% of them (11 requests) were addressed to the original Anzacs.net, 8% (1 request) were made to W3.org. The less responsive or slowest element that took the longest time to load (120 ms) belongs to the original domain Anzacs.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 20.5 kB (75%)

Content Size

27.2 kB

After Optimization

6.7 kB

  • HTML
  • Images

In fact, the total size of Anzacs.net main page is 27.2 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. Only 10% of websites need less resources to load. HTML takes 18.6 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 15.7 kB

  • Original 18.6 kB
  • After minification 16.6 kB
  • After compression 2.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 15.7 kB or 85% of the original size.

Image Optimization

-56%

Potential reduce by 4.8 kB

  • Original 8.6 kB
  • After minification 3.8 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, Anzacs needs image optimization as it can save up to 4.8 kB or 56% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

11

After Optimization

11

  • Images

The browser has sent 11 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Anzacs. According to our analytics all requests are already optimized.

Network Requests Diagram

anzacs.net

anzacs.net

120 ms

AnzacNEWbanner.gif

AnzacNEWbanner.gif

58 ms

Anzacs.gif

Anzacs.gif

44 ms

RedButton2.gif

RedButton2.gif

46 ms

RedBaron.gif

RedBaron.gif

46 ms

AudioPoems.gif

AudioPoems.gif

48 ms

BuglerLINK4.gif

BuglerLINK4.gif

45 ms

Indexes.gif

Indexes.gif

61 ms

service.gif

service.gif

61 ms

valid-html401

valid-html401

38 ms

Animations.gif

Animations.gif

53 ms

RedBar.jpg

RedBar.jpg

53 ms

Accessibility Review

anzacs.net accessibility score

84

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

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

SEO Factors

anzacs.net SEO score

69

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    US-ASCII

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Anzacs.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Anzacs.net main page’s claimed encoding is us-ascii. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

anzacs.net

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