Tools & Wizards About Us
innerfire.us screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

innerfire.us

INNER FIRE | Residential Healing Community | Addiction Recovery Without Medication

Page Load Speed

2 sec in total

First Response

522 ms

Resources Loaded

1.3 sec

Page Rendered

190 ms

innerfire.us screenshot

About Website

Visit innerfire.us now to see the best up-to-date INNER FIRE content and also check out these interesting facts you probably never knew about innerfire.us

Inner Fire is a proactive, healing community offering a choice for people to recover from debilitating and traumatic life challenges without the use of psychotropic medications.

Visit innerfire.us

Key Findings

We analyzed Innerfire.us page load time and found that the first response time was 522 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

innerfire.us performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

85/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

17/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.089

92/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

innerfire.us

522 ms

wp-emoji-release.min.js

97 ms

light_style.css

125 ms

css

22 ms

css

44 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 46% of them (23 requests) were addressed to the original Innerfire.us, 42% (21 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (522 ms) belongs to the original domain Innerfire.us.

Page Optimization Overview & Recommendations

Page size can be reduced by 346.6 kB (20%)

Content Size

1.7 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Innerfire.us main page is 1.7 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. 60% of websites need less resources to load. Images take 1.5 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 22.8 kB

  • Original 30.2 kB
  • After minification 28.6 kB
  • After compression 7.4 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 22.8 kB or 75% of the original size.

Image Optimization

-19%

Potential reduce by 278.8 kB

  • Original 1.5 MB
  • After minification 1.2 MB

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. Obviously, INNER FIRE needs image optimization as it can save up to 278.8 kB or 19% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-21%

Potential reduce by 24.2 kB

  • Original 117.6 kB
  • After minification 117.6 kB
  • After compression 93.3 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 24.2 kB or 21% of the original size.

CSS Optimization

-33%

Potential reduce by 20.8 kB

  • Original 62.2 kB
  • After minification 62.2 kB
  • After compression 41.4 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. Innerfire.us needs all CSS files to be minified and compressed as it can save up to 20.8 kB or 33% of the original size.

Requests Breakdown

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

Requests Now

27

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of INNER FIRE. 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 8 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

innerfire.us

innerfire.us

522 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

97 ms

light_style.css

light_style.css

125 ms

css

css

22 ms

css

css

44 ms

css

css

41 ms

style.css

style.css

125 ms

shortcodes.css

shortcodes.css

126 ms

shortcodes_responsive.css

shortcodes_responsive.css

128 ms

jquery.js

jquery.js

188 ms

jquery-migrate.min.js

jquery-migrate.min.js

156 ms

collapse.js

collapse.js

159 ms

jquery.fitvids.js

jquery.fitvids.js

159 ms

waypoints.min.js

waypoints.min.js

159 ms

jquery.magnific-popup.js

jquery.magnific-popup.js

159 ms

custom.js

custom.js

252 ms

wp-embed.min.js

wp-embed.min.js

220 ms

style.css

style.css

250 ms

2_inner_fire_logo_tagline_horiz_blue-1024x124.png

2_inner_fire_logo_tagline_horiz_blue-1024x124.png

67 ms

InnerFire-Sunset-background2.jpg

InnerFire-Sunset-background2.jpg

68 ms

trees-silo.png

trees-silo.png

378 ms

DSC_0170.jpg

DSC_0170.jpg

315 ms

timothy-hayes-interview.png

timothy-hayes-interview.png

315 ms

interview-pic.png

interview-pic.png

256 ms

paul-thomas-interview-screenshot-small.png

paul-thomas-interview-screenshot-small.png

257 ms

analytics.js

analytics.js

19 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7j.woff

15 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdo.woff

30 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wmRdo.woff

32 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo.woff

31 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo.woff

30 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdo.woff

61 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4k.woff

24 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4uaVQ.woff

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4k.woff

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4uaVQ.woff

42 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4k.woff

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4k.woff

40 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4uaVQ.woff

41 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4k.woff

42 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4uaVQ.woff

42 ms

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7psDQ.woff

6xK1dSBYKcSV-LCoeQqfX1RYOo3qPZ7psDQ.woff

78 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkidi18I.woff

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZMkidi18I.woff

142 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZYokSdi18I.woff

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZYokSdi18I.woff

149 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZY4lCdi18I.woff

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZY4lCdi18I.woff

148 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSdi18I.woff

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZclSdi18I.woff

147 ms

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZklydi18I.woff

6xKwdSBYKcSV-LCoeQqfX1RYOo3qPZZklydi18I.woff

96 ms

ETmodules_v2.ttf

ETmodules_v2.ttf

150 ms

collect

collect

32 ms

js

js

64 ms

Accessibility Review

innerfire.us 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.

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

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.

Best Practices

innerfire.us best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

innerfire.us SEO score

86

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

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Innerfire.us 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 Innerfire.us 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

innerfire.us

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