Tools & Wizards About Us
eoas.info screenshot

Report Summary

  • 73

    Performance

    Renders faster than
    82% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 95

    SEO

    Google-friendlier than
    90% of websites

eoas.info

Home - Encyclopedia of Australian Science and Innovation

Page Load Speed

1.8 sec in total

First Response

344 ms

Resources Loaded

1.1 sec

Page Rendered

349 ms

eoas.info screenshot

About Website

Visit eoas.info now to see the best up-to-date Eoas content for Australia and also check out these interesting facts you probably never knew about eoas.info

Home - Encyclopedia of Australian Science and Innovation, The Encyclopedia of Australian Science and Innovation is a biographical, bibliographical and archival database of Australian scientists with l...

Visit eoas.info

Key Findings

We analyzed Eoas.info page load time and found that the first response time was 344 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

eoas.info performance score

73

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

80/100

10%

LCP (Largest Contentful Paint)

Value4.2 s

44/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value140 ms

95/100

30%

CLS (Cumulative Layout Shift)

Value0.237

53/100

15%

TTI (Time to Interactive)

Value4.7 s

81/100

10%

Network Requests Diagram

eoas.info

344 ms

eoas.info

263 ms

css

41 ms

js

71 ms

normalize.css

88 ms

Our browser made a total of 30 requests to load all elements on the main page. We found that 43% of them (13 requests) were addressed to the original Eoas.info, 20% (6 requests) were made to Google.com and 13% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (344 ms) belongs to the original domain Eoas.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 34.2 kB (8%)

Content Size

414.5 kB

After Optimization

380.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eoas.info main page is 414.5 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. 30% of websites need less resources to load. Images take 193.5 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 19.1 kB

  • Original 28.6 kB
  • After minification 28.2 kB
  • After compression 9.5 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 19.1 kB or 67% of the original size.

Image Optimization

-3%

Potential reduce by 5.3 kB

  • Original 193.5 kB
  • After minification 188.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. Eoas images are well optimized though.

JavaScript Optimization

-2%

Potential reduce by 2.7 kB

  • Original 173.3 kB
  • After minification 173.3 kB
  • After compression 170.7 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

-38%

Potential reduce by 7.2 kB

  • Original 19.0 kB
  • After minification 18.2 kB
  • After compression 11.8 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. Eoas.info needs all CSS files to be minified and compressed as it can save up to 7.2 kB or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 12 (52%)

Requests Now

23

After Optimization

11

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eoas.info

eoas.info

344 ms

eoas.info

eoas.info

263 ms

css

css

41 ms

js

js

71 ms

normalize.css

normalize.css

88 ms

base.css

base.css

136 ms

layout.css

layout.css

196 ms

modules.css

modules.css

193 ms

modules-nav.css

modules-nav.css

194 ms

responsive-nav.js

responsive-nav.js

193 ms

cse.js

cse.js

46 ms

ga.js

ga.js

21 ms

logo.gif

logo.gif

166 ms

bullet.png

bullet.png

168 ms

EOAS_E-E_20240507.jpg

EOAS_E-E_20240507.jpg

293 ms

Logo_of_SUT.png

Logo_of_SUT.png

167 ms

cse_element__en.js

cse_element__en.js

28 ms

default+en.css

default+en.css

61 ms

default.css

default.css

64 ms

responsive-nav.png

responsive-nav.png

97 ms

__utm.gif

__utm.gif

38 ms

async-ads.js

async-ads.js

35 ms

branding.png

branding.png

30 ms

clear.png

clear.png

18 ms

nav_logo114.png

nav_logo114.png

18 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVQ.woff

22 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVQ.woff

25 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkWVAexg.woff

33 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjWVAexg.woff

39 ms

__utm.gif

__utm.gif

5 ms

Accessibility Review

eoas.info accessibility score

98

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Best Practices

eoas.info 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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

eoas.info SEO score

95

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

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 Eoas.info 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 Eoas.info 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

eoas.info

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