Report Summary

  • 53

    Performance

    Renders faster than
    71% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

inudge.net

Tonematrix

Page Load Speed

3.9 sec in total

First Response

358 ms

Resources Loaded

3.3 sec

Page Rendered

222 ms

inudge.net screenshot

About Website

Visit inudge.net now to see the best up-to-date Inudge content and also check out these interesting facts you probably never knew about inudge.net

A pentatonic step sequenzer which produces relaxing sonal patterns. Also available in the complete sequenzing studio app on audiotool.com

Visit inudge.net

Key Findings

We analyzed Inudge.net page load time and found that the first response time was 358 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

inudge.net performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

88/100

10%

LCP (Largest Contentful Paint)

Value2.9 s

80/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value153,310 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value175.6 s

0/100

10%

Network Requests Diagram

inudge.net

358 ms

tonematrix.audiotool.com

299 ms

jquery.min.js

32 ms

jquery.flash.js

94 ms

jquery.fancybox.js

185 ms

Our browser made a total of 46 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Inudge.net, 50% (23 requests) were made to Audiotool.com and 26% (12 requests) were made to Tonematrix.audiotool.com. The less responsive or slowest element that took the longest time to load (520 ms) relates to the external source Audiotool.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 136.7 kB (68%)

Content Size

202.3 kB

After Optimization

65.5 kB

In fact, the total size of Inudge.net main page is 202.3 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. 25% of websites need less resources to load. Javascripts take 177.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 13.1 kB

  • Original 17.2 kB
  • After minification 16.9 kB
  • After compression 4.1 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 13.1 kB or 76% of the original size.

JavaScript Optimization

-67%

Potential reduce by 118.4 kB

  • Original 177.8 kB
  • After minification 118.3 kB
  • After compression 59.4 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 118.4 kB or 67% of the original size.

CSS Optimization

-72%

Potential reduce by 5.3 kB

  • Original 7.3 kB
  • After minification 5.4 kB
  • After compression 2.1 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. Inudge.net needs all CSS files to be minified and compressed as it can save up to 5.3 kB or 72% of the original size.

Requests Breakdown

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

Requests Now

23

After Optimization

10

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

Accessibility Review

inudge.net accessibility score

71

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.

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.

Best Practices

inudge.net 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

High

Page has valid source maps

SEO Factors

inudge.net SEO score

91

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

    N/A

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Inudge.net 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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Inudge.net 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 Inudge. 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: