Tools & Wizards About Us
1in6.org screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 84

    SEO

    Google-friendlier than
    52% of websites

1in6.org

Support and survivor stories for men | 1in6

Page Load Speed

1.6 sec in total

First Response

24 ms

Resources Loaded

1.2 sec

Page Rendered

391 ms

1in6.org screenshot

About Website

Visit 1in6.org now to see the best up-to-date 1 In 6 content for United States and also check out these interesting facts you probably never knew about 1in6.org

Watch Bristlecone Project survivor stories and find confidential support, practical information, books, films, and recovery resources for men.

Visit 1in6.org

Key Findings

We analyzed 1in6.org page load time and found that the first response time was 24 ms and then it took 1.6 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

1in6.org performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value12.8 s

0/100

25%

SI (Speed Index)

Value8.4 s

18/100

10%

TBT (Total Blocking Time)

Value1,270 ms

19/100

30%

CLS (Cumulative Layout Shift)

Value0.201

61/100

15%

TTI (Time to Interactive)

Value14.9 s

8/100

10%

Network Requests Diagram

1in6.org

24 ms

1in6.org

98 ms

style.scss

79 ms

rau6qgp.js

125 ms

buttons.js

60 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 45% of them (29 requests) were addressed to the original 1in6.org, 16% (10 requests) were made to and 3% (2 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (470 ms) relates to the external source Connect.facebook.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 256.9 kB (25%)

Content Size

1.0 MB

After Optimization

770.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 1in6.org 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. 50% of websites need less resources to load. Images take 681.4 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 32.1 kB

  • Original 41.4 kB
  • After minification 36.0 kB
  • After compression 9.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. This page needs HTML code to be minified as it can gain 5.4 kB, which is 13% 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 32.1 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 32.3 kB

  • Original 681.4 kB
  • After minification 649.1 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. 1 In 6 images are well optimized though.

JavaScript Optimization

-57%

Potential reduce by 129.3 kB

  • Original 228.4 kB
  • After minification 223.7 kB
  • After compression 99.1 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 129.3 kB or 57% of the original size.

CSS Optimization

-83%

Potential reduce by 63.2 kB

  • Original 76.5 kB
  • After minification 75.2 kB
  • After compression 13.3 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. 1in6.org needs all CSS files to be minified and compressed as it can save up to 63.2 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 26 (52%)

Requests Now

50

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

1in6.org

1in6.org

24 ms

1in6.org

1in6.org

98 ms

style.scss

style.scss

79 ms

rau6qgp.js

rau6qgp.js

125 ms

buttons.js

buttons.js

60 ms

jquery.js

jquery.js

39 ms

jquery-migrate.min.js

jquery-migrate.min.js

39 ms

jquery.json.js

jquery.json.js

37 ms

gravityforms.min.js

gravityforms.min.js

35 ms

conditional_logic.min.js

conditional_logic.min.js

37 ms

style.css

style.css

39 ms

112 ms

wp-embed.min.js

wp-embed.min.js

38 ms

jquery.cookie.min.js

jquery.cookie.min.js

45 ms

respond.min.js

respond.min.js

49 ms

1in6.js

1in6.js

39 ms

198 ms

analytics.js

analytics.js

96 ms

all.js

all.js

470 ms

getAllAppDefault.esi

getAllAppDefault.esi

56 ms

noise-light-grey.jpg

noise-light-grey.jpg

14 ms

1in6logo-print.gif

1in6logo-print.gif

11 ms

noise-dark-grey.jpg

noise-dark-grey.jpg

14 ms

sprite.png

sprite.png

36 ms

landing-block-back.png

landing-block-back.png

24 ms

home-block-welcome-back.png

home-block-welcome-back.png

38 ms

home-supportline-back-gn.jpg

home-supportline-back-gn.jpg

37 ms

home-block-library-back.jpg

home-block-library-back.jpg

37 ms

PeterThumbnail-85x60.jpg

PeterThumbnail-85x60.jpg

37 ms

soundart-85x60.jpg

soundart-85x60.jpg

37 ms

ThumbLatino-85x60.jpg

ThumbLatino-85x60.jpg

38 ms

home-community-back-gn.jpg

home-community-back-gn.jpg

39 ms

hpphoto_for-men.png

hpphoto_for-men.png

41 ms

hpphoto_for-partners-and-friends.png

hpphoto_for-partners-and-friends.png

45 ms

hpphoto_for-professionals.png

hpphoto_for-professionals.png

47 ms

home-banner-community.png

home-banner-community.png

40 ms

d

d

188 ms

collect

collect

13 ms

collect

collect

64 ms

getSegment.php

getSegment.php

41 ms

t.dhj

t.dhj

27 ms

pixel

pixel

52 ms

t.dhj

t.dhj

16 ms

hbpix

hbpix

311 ms

cm

cm

194 ms

adxmapping.php

adxmapping.php

141 ms

fP+IDbeK3HQ==

fP+IDbeK3HQ==

14 ms

fP+IDbeK3HQ==

fP+IDbeK3HQ==

14 ms

4gNt4rcd

4gNt4rcd

13 ms

iA23itx0=

iA23itx0=

13 ms

iA23itx0=

iA23itx0=

12 ms

iA23itx0=

iA23itx0=

12 ms

4gNt4rcd

4gNt4rcd

11 ms

t9thp11222OvffaH93HQIYcdcdQxx51w0imnnXHWOeddcNEll11x1TXX5brhplvhjd1x1z157nsgX4GHCj1S5LEnnnrmuRdeeuW1N956570PPv4EiV9utQAAAA==

t9thp11222OvffaH93HQIYcdcdQxx51w0imnnXHWOeddcNEll11x1TXX5brhplvhjd1x1z157nsgX4GHCj1S5LEnnnrmuRdeeuW1N956570PPv4EiV9utQAAAA==

11 ms

f3n7gBGbqz2wAAAA==

f3n7gBGbqz2wAAAA==

9 ms

f3n7gBGbqz2wAAAA==

f3n7gBGbqz2wAAAA==

8 ms

s-3271.xgi

s-3271.xgi

10 ms

p.gif

p.gif

153 ms

6 ms

80 ms

xrefid.xgi

xrefid.xgi

48 ms

124 ms

xd_arbiter.php

xd_arbiter.php

427 ms

img;m=11022203137504;cache=

img;m=11022203137504;cache=

103 ms

Accessibility Review

1in6.org accessibility score

84

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

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

Links do not have a discernible name

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

1in6.org best practices score

67

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

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

1in6.org SEO score

84

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

High

Tap targets are not sized appropriately

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 1in6.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 1in6.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

1in6.org

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