Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

aeganz.com

Welcome to Access Engineering | Leaders in Scaffold & Access in Perth

Page Load Speed

10 sec in total

First Response

1.2 sec

Resources Loaded

8.3 sec

Page Rendered

490 ms

aeganz.com screenshot

About Website

Visit aeganz.com now to see the best up-to-date Aeganz content and also check out these interesting facts you probably never knew about aeganz.com

Access Engineering Group (AEG) specialises in providing access systems for our trade based Scaffolders and Rope Access Technicians in Perth.

Visit aeganz.com

Key Findings

We analyzed Aeganz.com page load time and found that the first response time was 1.2 sec and then it took 8.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

aeganz.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.7 s

5/100

10%

LCP (Largest Contentful Paint)

Value24.7 s

0/100

25%

SI (Speed Index)

Value11.8 s

4/100

10%

TBT (Total Blocking Time)

Value1,650 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.182

67/100

15%

TTI (Time to Interactive)

Value19.9 s

2/100

10%

Network Requests Diagram

www.aeganz.com

1229 ms

css2

29 ms

css2

41 ms

84qbp.css

213 ms

84qbp.css

433 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 71% of them (61 requests) were addressed to the original Aeganz.com, 13% (11 requests) were made to Fonts.gstatic.com and 7% (6 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Aeganz.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 108.3 kB (2%)

Content Size

4.8 MB

After Optimization

4.7 MB

In fact, the total size of Aeganz.com main page is 4.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 4.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 48.5 kB

  • Original 59.3 kB
  • After minification 56.9 kB
  • After compression 10.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 48.5 kB or 82% of the original size.

Image Optimization

-1%

Potential reduce by 50.6 kB

  • Original 4.4 MB
  • After minification 4.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. Aeganz images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 6.8 kB

  • Original 244.8 kB
  • After minification 244.8 kB
  • After compression 238.1 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

-2%

Potential reduce by 2.4 kB

  • Original 108.9 kB
  • After minification 108.9 kB
  • After compression 106.6 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. Aeganz.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (19%)

Requests Now

73

After Optimization

59

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

Accessibility Review

aeganz.com accessibility score

57

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

<frame> or <iframe> elements do not have a title

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

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

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

aeganz.com 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

aeganz.com SEO score

100

Search Engine Optimization Advices

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Aeganz.com 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 Aeganz.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

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