Report Summary

  • 41

    Performance

    Renders faster than
    60% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

forerunner.com.au

Home - Forerunner Computer Systems

Page Load Speed

4.5 sec in total

First Response

457 ms

Resources Loaded

3.4 sec

Page Rendered

583 ms

About Website

Welcome to forerunner.com.au homepage info - get ready to check Forerunner best content right away, or after learning these important things about forerunner.com.au

Forerunner Computer Systems is leading the way in IT and Web Solutions in Adelaide. Forerunner specialises in IT, VoIP systems, web design and development.

Visit forerunner.com.au

Key Findings

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

Performance Metrics

forerunner.com.au performance score

41

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

52/100

10%

LCP (Largest Contentful Paint)

Value9.8 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value540 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.06

98/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

forerunner.com.au

457 ms

forerunner.com.au

869 ms

autoptimize_c55d5d13c4928f582da9790f6b32989a.css

43 ms

autoptimize_single_959dda4eaac2b416673169ffe5ad9d7f.css

87 ms

autoptimize_single_70d0849894cf1ce39241729d7d7ee6f8.css

88 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 62% of them (23 requests) were addressed to the original Forerunner.com.au, 32% (12 requests) were made to Fonts.gstatic.com and 3% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.7 sec) belongs to the original domain Forerunner.com.au.

Page Optimization Overview & Recommendations

Page size can be reduced by 105.1 kB (9%)

Content Size

1.1 MB

After Optimization

1.0 MB

In fact, the total size of Forerunner.com.au main page is 1.1 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. 70% of websites need less resources to load. Images take 762.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 105.1 kB

  • Original 127.2 kB
  • After minification 127.2 kB
  • After compression 22.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. 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 105.1 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 762.3 kB
  • After minification 762.3 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. Forerunner images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 32 B

  • Original 146.3 kB
  • After minification 146.3 kB
  • After compression 146.2 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.

CSS Optimization

-0%

Potential reduce by 36 B

  • Original 95.3 kB
  • After minification 95.3 kB
  • After compression 95.2 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. Forerunner.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 9 (47%)

Requests Now

19

After Optimization

10

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

Accessibility Review

forerunner.com.au accessibility score

95

Accessibility Issues

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

High

Links do not have a discernible name

Best Practices

forerunner.com.au best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

forerunner.com.au SEO score

89

Search Engine Optimization Advices

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

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