Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 56

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 0

    Best Practices

  • 77

    SEO

    Google-friendlier than
    36% of websites

Page Load Speed

2.4 sec in total

First Response

28 ms

Resources Loaded

2.1 sec

Page Rendered

317 ms

iovs.org screenshot

About Website

Welcome to iovs.org homepage info - get ready to check Iovs best content for United States right away, or after learning these important things about iovs.org

Visit iovs.org

Key Findings

We analyzed Iovs.org page load time and found that the first response time was 28 ms and then it took 2.4 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster. This domain responded with an error, which can significantly jeopardize Iovs.org rating and web reputation

Performance Metrics

iovs.org performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

90/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value4.3 s

75/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value11.3 s

19/100

10%

Network Requests Diagram

iovs.org

28 ms

iovs.arvojournals.org

1359 ms

css

34 ms

shared-css

19 ms

pages-with-minimal-css

12 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Iovs.org, 59% (32 requests) were made to Iovs.arvojournals.org and 7% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Iovs.arvojournals.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 344.2 kB (69%)

Content Size

495.8 kB

After Optimization

151.6 kB

In fact, the total size of Iovs.org main page is 495.8 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. 55% of websites need less resources to load. Javascripts take 210.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 42.3 kB

  • Original 54.3 kB
  • After minification 40.8 kB
  • After compression 11.9 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 13.5 kB, which is 25% 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 42.3 kB or 78% of the original size.

Image Optimization

-9%

Potential reduce by 3.7 kB

  • Original 39.9 kB
  • After minification 36.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. Iovs images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 136.1 kB

  • Original 210.7 kB
  • After minification 209.8 kB
  • After compression 74.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 136.1 kB or 65% of the original size.

CSS Optimization

-85%

Potential reduce by 162.1 kB

  • Original 190.9 kB
  • After minification 190.3 kB
  • After compression 28.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. Iovs.org needs all CSS files to be minified and compressed as it can save up to 162.1 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (57%)

Requests Now

30

After Optimization

13

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

Accessibility Review

iovs.org accessibility score

56

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.

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

<dl>'s do not contain only properly-ordered <dt> and <dd> groups, <script>, <template> or <div> elements.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

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.

SEO Factors

iovs.org SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Iovs.org 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), while the claimed language is English. Our system also found out that Iovs.org 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 description is not detected on the main page of Iovs. 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: