Tools & Wizards About Us
iris.edu screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

iris.edu

SAGE

Page Load Speed

1.9 sec in total

First Response

137 ms

Resources Loaded

1.4 sec

Page Rendered

346 ms

iris.edu screenshot

About Website

Visit iris.edu now to see the best up-to-date Iris content for Japan and also check out these interesting facts you probably never knew about iris.edu

Seismological Facility for the Advancement of Geoscience (SAGE) is a distributed, multi-user national facility operated by EarthScope that provides state of-the-art seismic and related geophysical ins...

Visit iris.edu

Key Findings

We analyzed Iris.edu page load time and found that the first response time was 137 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

iris.edu performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value4.2 s

77/100

10%

TBT (Total Blocking Time)

Value240 ms

85/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.0 s

42/100

10%

Network Requests Diagram

137 ms

435 ms

bootstrap.min.css

44 ms

55 ms

jquery-ui.min.css

36 ms

Our browser made a total of 37 requests to load all elements on the main page. We found that 51% of them (19 requests) were addressed to the original Iris.edu, 14% (5 requests) were made to Fonts.gstatic.com and 11% (4 requests) were made to Cdnjs.cloudflare.com. The less responsive or slowest element that took the longest time to load (534 ms) relates to the external source Ds.iris.edu.

Page Optimization Overview & Recommendations

Page size can be reduced by 48.7 kB (5%)

Content Size

1.0 MB

After Optimization

956.4 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Iris.edu main page is 1.0 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. 40% of websites need less resources to load. Images take 953.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 35.5 kB

  • Original 44.1 kB
  • After minification 35.4 kB
  • After compression 8.6 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 8.7 kB, which is 20% 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 35.5 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 13.2 kB

  • Original 953.3 kB
  • After minification 940.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. Iris images are well optimized though.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 7.6 kB
  • After minification 7.6 kB
  • After compression 7.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. Iris.edu has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 10 (34%)

Requests Now

29

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

137 ms

435 ms

bootstrap.min.css

bootstrap.min.css

44 ms

55 ms

jquery-ui.min.css

jquery-ui.min.css

36 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

41 ms

bootstrap.min.js

bootstrap.min.js

52 ms

jquery-ui.min.js

jquery-ui.min.js

49 ms

js.cookie.min.js

js.cookie.min.js

48 ms

jquery.inputmask.bundle.min.js

jquery.inputmask.bundle.min.js

52 ms

jquery.tablesorter.min.js

jquery.tablesorter.min.js

62 ms

animate.min.css

animate.min.css

60 ms

css

css

35 ms

gtm.js

gtm.js

60 ms

nsf-x1.png

nsf-x1.png

34 ms

seismon_transp.gif

seismon_transp.gif

534 ms

sage-x1.png

sage-x1.png

58 ms

esc_white-x1.png

esc_white-x1.png

76 ms

white-waves.png

white-waves.png

144 ms

Alaska-panorama3.jpg

Alaska-panorama3.jpg

330 ms

curtain-1423196.jpg

curtain-1423196.jpg

169 ms

05-31-2018-IMG_b.jpg

05-31-2018-IMG_b.jpg

231 ms

eq-resources3.png

eq-resources3.png

144 ms

230828_Indonesia-500x375.png

230828_Indonesia-500x375.png

207 ms

Screen_Shot_2022-08-24_at_7.44.31_AM_1_thumb.jpg

Screen_Shot_2022-08-24_at_7.44.31_AM_1_thumb.jpg

197 ms

OnePager7.jpg

OnePager7.jpg

207 ms

A_004A_seissig_elk_thumbnail.jpg

A_004A_seissig_elk_thumbnail.jpg

207 ms

solial-bottom.png

solial-bottom.png

229 ms

footer-nsf-x1.png

footer-nsf-x1.png

234 ms

footer-sage-x1.png

footer-sage-x1.png

234 ms

footer_esc_white-x1.png

footer_esc_white-x1.png

234 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

25 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

37 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

51 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

51 ms

glyphicons-halflings-regular.woff

glyphicons-halflings-regular.woff

12 ms

Accessibility Review

iris.edu accessibility score

76

Accessibility Issues

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

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

iris.edu best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

iris.edu SEO score

89

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

Image elements do not have [alt] attributes

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

    N/A

  • Encoding

    UTF-8

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

iris.edu

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