Tools & Wizards About Us
safeplace.org screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

safeplace.org

Home Page - The SAFE Alliance

Page Load Speed

7 sec in total

First Response

656 ms

Resources Loaded

6.2 sec

Page Rendered

114 ms

safeplace.org screenshot

About Website

Click here to check amazing SAFE Place content for United States. Otherwise, check out these important facts you probably never knew about safeplace.org

The SAFE Alliance exists to stop abuse for everyone by serving the survivors of child abuse, sexual assault, trafficking, and domestic violence.

Visit safeplace.org

Key Findings

We analyzed Safeplace.org page load time and found that the first response time was 656 ms and then it took 6.3 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

safeplace.org performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.6 s

5/100

10%

LCP (Largest Contentful Paint)

Value17.2 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value11,520 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.08

94/100

15%

TTI (Time to Interactive)

Value25.0 s

0/100

10%

Network Requests Diagram

safeplace.org

656 ms

1870 ms

wp-emoji-release.min.js

100 ms

toolbar.css

229 ms

style.css

201 ms

Our browser made a total of 91 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Safeplace.org, 59% (54 requests) were made to Safeaustin.org and 8% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.9 sec) relates to the external source Safeaustin.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 650.3 kB (62%)

Content Size

1.0 MB

After Optimization

391.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Safeplace.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. 55% of websites need less resources to load. CSS take 483.8 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 60.7 kB

  • Original 73.8 kB
  • After minification 70.7 kB
  • After compression 13.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 60.7 kB or 82% of the original size.

Image Optimization

-28%

Potential reduce by 32.5 kB

  • Original 116.2 kB
  • After minification 83.7 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. Obviously, SAFE Place needs image optimization as it can save up to 32.5 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-49%

Potential reduce by 178.7 kB

  • Original 368.4 kB
  • After minification 351.2 kB
  • After compression 189.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 178.7 kB or 49% of the original size.

CSS Optimization

-78%

Potential reduce by 378.4 kB

  • Original 483.8 kB
  • After minification 437.6 kB
  • After compression 105.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. Safeplace.org needs all CSS files to be minified and compressed as it can save up to 378.4 kB or 78% of the original size.

Requests Breakdown

Number of requests can be reduced by 62 (77%)

Requests Now

81

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

safeplace.org

safeplace.org

656 ms

1870 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

100 ms

toolbar.css

toolbar.css

229 ms

style.css

style.css

201 ms

farbtastic.css

farbtastic.css

224 ms

animate.css

animate.css

217 ms

frontend.css

frontend.css

184 ms

style.css

style.css

290 ms

light_style.css

light_style.css

272 ms

font-awesome.min.css

font-awesome.min.css

285 ms

post-tiles.css

post-tiles.css

305 ms

wpa-style.css

wpa-style.css

324 ms

styles.css

styles.css

333 ms

tribe-events-full.min.css

tribe-events-full.min.css

347 ms

wp-email-capture-styles.css

wp-email-capture-styles.css

414 ms

css

css

25 ms

font-awesome.min.css

font-awesome.min.css

14 ms

style.css

style.css

407 ms

responsive.dataTables.min.css

responsive.dataTables.min.css

385 ms

tablepress-combined.min.css

tablepress-combined.min.css

413 ms

styles

styles

1519 ms

asmh.css

asmh.css

469 ms

0a8dd671bf298fb1870d0fc3bfb9eea0a6fcaf3c.css

0a8dd671bf298fb1870d0fc3bfb9eea0a6fcaf3c.css

460 ms

genericons.css

genericons.css

488 ms

jetpack.css

jetpack.css

492 ms

tablepress-responsive-flip.min.css

tablepress-responsive-flip.min.css

499 ms

jquery.js

jquery.js

674 ms

jquery-migrate.min.js

jquery-migrate.min.js

541 ms

flags.js

flags.js

574 ms

toolbar.js

toolbar.js

579 ms

load-toolbar.js

load-toolbar.js

583 ms

frontend.js

frontend.js

622 ms

front.js

front.js

671 ms

skiplinks.webkit.js

skiplinks.webkit.js

651 ms

scripts.js

scripts.js

685 ms

asmh.js

asmh.js

707 ms

www.safeaustin.org

www.safeaustin.org

1759 ms

element.js

element.js

33 ms

collapse.js

collapse.js

749 ms

devicepx-jetpack.js

devicepx-jetpack.js

8 ms

gprofiles.js

gprofiles.js

57 ms

e-201611.js

e-201611.js

7 ms

wpa.labels.js

wpa.labels.js

741 ms

longdesc.button.js

longdesc.button.js

666 ms

wpgroho.js

wpgroho.js

618 ms

jquery.cycle2.min.js

jquery.cycle2.min.js

635 ms

wp-embed.min.js

wp-embed.min.js

640 ms

sharing.js

sharing.js

630 ms

analytics.js

analytics.js

8 ms

all-symbols-2014-K.png

all-symbols-2014-K.png

135 ms

facebook.png

facebook.png

278 ms

safe-web-header1.png

safe-web-header1.png

120 ms

facebook.png

facebook.png

105 ms

twitter.png

twitter.png

109 ms

linkedin.png

linkedin.png

105 ms

youtube.png

youtube.png

110 ms

twitter.png

twitter.png

279 ms

instagram.png

instagram.png

284 ms

linkedin.png

linkedin.png

280 ms

collect

collect

22 ms

BCFBp4rt5gxxFrX6F12DKvesZW2xOQ-xsNqO47m55DA.woff

BCFBp4rt5gxxFrX6F12DKvesZW2xOQ-xsNqO47m55DA.woff

11 ms

BVtM30trf7q_jfqYeHfjtA.woff

BVtM30trf7q_jfqYeHfjtA.woff

21 ms

9k-RPmcnxYEPm8CNFsH2gg.woff

9k-RPmcnxYEPm8CNFsH2gg.woff

18 ms

KT3KS9Aol4WfR6Vas8kNcg.woff

KT3KS9Aol4WfR6Vas8kNcg.woff

17 ms

Oiz0tNwvC-Nd29SBQWfWTBsxEYwM7FgeyaSgU71cLG0.woff

Oiz0tNwvC-Nd29SBQWfWTBsxEYwM7FgeyaSgU71cLG0.woff

17 ms

Genericons.svg

Genericons.svg

188 ms

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

8AAnjaY2BgYGQAgosrjpwF0ZcUq9bCaABTzgdAAAA=

2 ms

2HG_tEPiQ4Z6795cGfdivD8E0i7KZn-EPnyo3HZu7kw.woff

2HG_tEPiQ4Z6795cGfdivD8E0i7KZn-EPnyo3HZu7kw.woff

17 ms

oUan5VrEkpzIazlUe5ieaA.woff

oUan5VrEkpzIazlUe5ieaA.woff

17 ms

loading.gif

loading.gif

148 ms

translateelement.css

translateelement.css

73 ms

main.js

main.js

107 ms

tribe-events-full-mobile.min.css

tribe-events-full-mobile.min.css

290 ms

widgets.js

widgets.js

248 ms

hovercard.css

hovercard.css

86 ms

services.css

services.css

88 ms

share

share

150 ms

g.gif

g.gif

66 ms

count.json

count.json

68 ms

graph.facebook.com

graph.facebook.com

186 ms

flags.png

flags.png

227 ms

SAFE-Logo-TAG-RGB.png

SAFE-Logo-TAG-RGB.png

90 ms

g.gif

g.gif

50 ms

g.gif

g.gif

51 ms

search-font.woff

search-font.woff

120 ms

element_main.js

element_main.js

72 ms

g.gif

g.gif

5 ms

translate_24dp.png

translate_24dp.png

28 ms

l

l

47 ms

googlelogo_color_42x16dp.png

googlelogo_color_42x16dp.png

23 ms

Accessibility Review

safeplace.org accessibility score

80

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

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

High

Some elements have a [tabindex] value greater than 0

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.

Best Practices

safeplace.org best practices score

75

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

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

safeplace.org SEO score

83

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Safeplace.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 Safeplace.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

safeplace.org

Open Graph data is detected on the main page of SAFE Place. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: