Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 54

    SEO

    Google-friendlier than
    19% of websites

Page Load Speed

5.3 sec in total

First Response

660 ms

Resources Loaded

4.6 sec

Page Rendered

93 ms

idgee.com.au screenshot

About Website

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

Visit idgee.com.au

Key Findings

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

Performance Metrics

idgee.com.au performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.017

100/100

15%

TTI (Time to Interactive)

Value4.1 s

86/100

10%

Network Requests Diagram

idgee.com.au

660 ms

idgee.com.au

861 ms

css

18 ms

bootstrap.min.css

1538 ms

common.css

1756 ms

Our browser made a total of 9 requests to load all elements on the main page. We found that 89% of them (8 requests) were addressed to the original Idgee.com.au, 11% (1 request) were made to Fonts.bunny.net. The less responsive or slowest element that took the longest time to load (3.1 sec) belongs to the original domain Idgee.com.au.

Page Optimization Overview & Recommendations

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

Content Size

191.5 kB

After Optimization

175.2 kB

In fact, the total size of Idgee.com.au main page is 191.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. Images take 161.8 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 1.3 kB

  • Original 1.7 kB
  • After minification 1.5 kB
  • After compression 446 B

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 1.3 kB or 74% of the original size.

Image Optimization

-9%

Potential reduce by 14.6 kB

  • Original 161.8 kB
  • After minification 147.2 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. Idgee images are well optimized though.

CSS Optimization

-2%

Potential reduce by 430 B

  • Original 27.9 kB
  • After minification 27.9 kB
  • After compression 27.5 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. Idgee.com.au has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 4 (67%)

Requests Now

6

After Optimization

2

The browser has sent 6 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Idgee. 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 CSS and as a result speed up the page load time.

Accessibility Review

idgee.com.au accessibility score

74

Accessibility Issues

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

Document doesn't have a <title> element

High

Links do not have a discernible name

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

idgee.com.au best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

SEO Factors

idgee.com.au SEO score

54

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

Document doesn't have a <title> element

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

robots.txt is not valid

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Idgee.com.au can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Idgee.com.au main page’s claimed encoding is . 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

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