Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 100

    Accessibility

    Visual factors better than
    that of 97% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

users.on.net

NodeSupport / Guides / Internode Members Webspace End of Life | Internode

Page Load Speed

7 sec in total

First Response

1.6 sec

Resources Loaded

5.3 sec

Page Rendered

113 ms

users.on.net screenshot

About Website

Click here to check amazing Users On content for Australia. Otherwise, check out these important facts you probably never knew about users.on.net

Internode Personal User Webspace

Visit users.on.net

Key Findings

We analyzed Users.on.net page load time and found that the first response time was 1.6 sec and then it took 5.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

users.on.net performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.6 s

100/100

10%

LCP (Largest Contentful Paint)

Value0.6 s

100/100

25%

SI (Speed Index)

Value0.9 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value0.6 s

100/100

10%

Network Requests Diagram

users.on.net

1560 ms

globals.js

545 ms

general.css

1018 ms

home.css

1031 ms

internode_logo.gif

486 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Users.on.net, 97% (31 requests) were made to Internode.on.net. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Internode.on.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 37.7 kB (53%)

Content Size

70.8 kB

After Optimization

33.1 kB

In fact, the total size of Users.on.net main page is 70.8 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. CSS take 32.4 kB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 9.5 kB

  • Original 12.7 kB
  • After minification 11.0 kB
  • After compression 3.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. This page needs HTML code to be minified as it can gain 1.7 kB, which is 13% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 9.5 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 24.0 kB
  • After minification 24.0 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. Users On images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 1.1 kB

  • Original 1.7 kB
  • After minification 1.3 kB
  • After compression 525 B

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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.1 kB or 68% of the original size.

CSS Optimization

-84%

Potential reduce by 27.1 kB

  • Original 32.4 kB
  • After minification 26.1 kB
  • After compression 5.3 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. Users.on.net needs all CSS files to be minified and compressed as it can save up to 27.1 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (71%)

Requests Now

31

After Optimization

9

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

Accessibility Review

users.on.net accessibility score

100

Accessibility Issues

Best Practices

users.on.net 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

SEO Factors

users.on.net SEO score

58

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Users.on.net 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 Users.on.net main page’s claimed encoding is iso-8859-1. 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 Users On. 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: