Tools & Wizards About Us
inodes.org screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    66% of other websites

  • 76

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

inodes.org

John's Tidbits

Page Load Speed

6.4 sec in total

First Response

439 ms

Resources Loaded

5.3 sec

Page Rendered

681 ms

inodes.org screenshot

About Website

Click here to check amazing Inodes content. Otherwise, check out these important facts you probably never knew about inodes.org

Development, Trouble-shooting and Random thoughts…

Visit inodes.org

Key Findings

We analyzed Inodes.org page load time and found that the first response time was 439 ms and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

inodes.org performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value6.5 s

9/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value350 ms

73/100

30%

CLS (Cumulative Layout Shift)

Value0.029

100/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

inodes.org

439 ms

inodes.org

1309 ms

style.min.css

399 ms

mediaelementplayer-legacy.min.css

595 ms

wp-mediaelement.min.css

597 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 92% of them (33 requests) were addressed to the original Inodes.org, 3% (1 request) were made to Googletagmanager.com and 3% (1 request) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (1.8 sec) relates to the external source Wordpress.inodes.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 185.6 kB (16%)

Content Size

1.1 MB

After Optimization

954.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Inodes.org main page is 1.1 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. 35% of websites need less resources to load. Images take 821.4 kB which makes up the majority of the site volume.

HTML Optimization

-66%

Potential reduce by 119.8 kB

  • Original 182.1 kB
  • After minification 179.3 kB
  • After compression 62.3 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 119.8 kB or 66% of the original size.

Image Optimization

-4%

Potential reduce by 34.9 kB

  • Original 821.4 kB
  • After minification 786.5 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. Inodes images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 10.8 kB

  • Original 71.8 kB
  • After minification 71.8 kB
  • After compression 61.0 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 10.8 kB or 15% of the original size.

CSS Optimization

-31%

Potential reduce by 20.2 kB

  • Original 65.1 kB
  • After minification 65.1 kB
  • After compression 45.0 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. Inodes.org needs all CSS files to be minified and compressed as it can save up to 20.2 kB or 31% of the original size.

Requests Breakdown

Number of requests can be reduced by 21 (81%)

Requests Now

26

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

inodes.org

inodes.org

439 ms

inodes.org

inodes.org

1309 ms

style.min.css

style.min.css

399 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

595 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

597 ms

prism-a11y-dark.css

prism-a11y-dark.css

597 ms

wp-syntax.css

wp-syntax.css

598 ms

font-libre-franklin.css

font-libre-franklin.css

601 ms

style.css

style.css

801 ms

blocks.css

blocks.css

791 ms

colors-dark.css

colors-dark.css

792 ms

style.css

style.css

794 ms

social-icons.css

social-icons.css

796 ms

jquery.min.js

jquery.min.js

999 ms

jquery-migrate.min.js

jquery-migrate.min.js

988 ms

global.js

global.js

989 ms

navigation.js

navigation.js

991 ms

js

js

69 ms

swiper-bundle.css

swiper-bundle.css

994 ms

jetpack-carousel.css

jetpack-carousel.css

1086 ms

prism.js

prism.js

1185 ms

wp-syntax.js

wp-syntax.js

1191 ms

jquery.scrollTo.js

jquery.scrollTo.js

1192 ms

e-202446.js

e-202446.js

16 ms

jetpack-carousel.min.js

jetpack-carousel.min.js

1193 ms

cropped-0X6A2969-3.jpg

cropped-0X6A2969-3.jpg

1790 ms

Cover-Page-Panel-1-V2-1024x1024.png

Cover-Page-Panel-1-V2-1024x1024.png

1000 ms

aws-profiles.gif

aws-profiles.gif

399 ms

libre-franklin-all-400-normal.woff

libre-franklin-all-400-normal.woff

488 ms

libre-franklin-all-300-normal.woff

libre-franklin-all-300-normal.woff

497 ms

libre-franklin-all-600-normal.woff

libre-franklin-all-600-normal.woff

498 ms

libre-franklin-all-800-normal.woff

libre-franklin-all-800-normal.woff

301 ms

libre-franklin-all-400-italic.woff

libre-franklin-all-400-italic.woff

515 ms

libre-franklin-all-300-italic.woff

libre-franklin-all-300-italic.woff

536 ms

libre-franklin-all-600-italic.woff

libre-franklin-all-600-italic.woff

687 ms

libre-franklin-all-800-italic.woff

libre-franklin-all-800-italic.woff

694 ms

Accessibility Review

inodes.org accessibility score

76

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

button, link, and menuitem elements do not have accessible names.

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.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Some elements have a [tabindex] value greater than 0

Best Practices

inodes.org 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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

inodes.org SEO score

100

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

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 Inodes.org 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 Inodes.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

inodes.org

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