Tools & Wizards About Us
nationalmarriage.com screenshot

Report Summary

  • 20

    Performance

    Renders faster than
    37% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

nationalmarriage.com

Home - Hope Restored : A Marriage Intensive Experience

Page Load Speed

22.9 sec in total

First Response

188 ms

Resources Loaded

21.9 sec

Page Rendered

791 ms

nationalmarriage.com screenshot

About Website

Welcome to nationalmarriage.com homepage info - get ready to check National Marriage best content for United States right away, or after learning these important things about nationalmarriage.com

Hope Restored marriage intensives. Avoid divorce and fix your marriage with a year of marriage counseling in days. Licensed counselors. 3 retreat locations.

Visit nationalmarriage.com

Key Findings

We analyzed Nationalmarriage.com page load time and found that the first response time was 188 ms and then it took 22.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

nationalmarriage.com performance score

20

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

21/100

10%

LCP (Largest Contentful Paint)

Value8.1 s

2/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value3,050 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value20.4 s

2/100

10%

Network Requests Diagram

hoperestored.focusonthefamily.com

188 ms

optimize.js

80 ms

fotf-source-code-pass-through-public.css

42 ms

geotarget-public.min.css

41 ms

rate-my-post.css

221 ms

Our browser made a total of 166 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Nationalmarriage.com, 9% (15 requests) were made to Fonts.gstatic.com and 4% (7 requests) were made to Fotf.tfaforms.net. The less responsive or slowest element that took the longest time to load (20.1 sec) relates to the external source Ps.eyeota.net.

Page Optimization Overview & Recommendations

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

Content Size

844.0 kB

After Optimization

712.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nationalmarriage.com main page is 844.0 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 302.4 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 115.5 kB

  • Original 143.5 kB
  • After minification 139.1 kB
  • After compression 28.0 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 115.5 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 259.4 kB
  • After minification 259.4 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. National Marriage images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 9.4 kB

  • Original 302.4 kB
  • After minification 302.4 kB
  • After compression 292.9 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. This website has mostly compressed JavaScripts.

CSS Optimization

-5%

Potential reduce by 6.6 kB

  • Original 138.7 kB
  • After minification 138.6 kB
  • After compression 132.2 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. Nationalmarriage.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 115 (89%)

Requests Now

129

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hoperestored.focusonthefamily.com

hoperestored.focusonthefamily.com

188 ms

optimize.js

optimize.js

80 ms

fotf-source-code-pass-through-public.css

fotf-source-code-pass-through-public.css

42 ms

geotarget-public.min.css

geotarget-public.min.css

41 ms

rate-my-post.css

rate-my-post.css

221 ms

theme.min.css

theme.min.css

53 ms

style.css

style.css

51 ms

style.min.css

style.min.css

41 ms

header-footer.min.css

header-footer.min.css

109 ms

elementor-icons.min.css

elementor-icons.min.css

70 ms

frontend.min.css

frontend.min.css

73 ms

swiper.min.css

swiper.min.css

74 ms

post-2540.css

post-2540.css

108 ms

frontend.min.css

frontend.min.css

113 ms

all.min.css

all.min.css

109 ms

v4-shims.min.css

v4-shims.min.css

261 ms

global.css

global.css

126 ms

post-6.css

post-6.css

124 ms

post-3249.css

post-3249.css

132 ms

post-123.css

post-123.css

133 ms

post-1054.css

post-1054.css

132 ms

general.min.css

general.min.css

140 ms

css

css

70 ms

fontawesome.min.css

fontawesome.min.css

143 ms

solid.min.css

solid.min.css

149 ms

regular.min.css

regular.min.css

145 ms

jquery.min.js

jquery.min.js

179 ms

jquery-migrate.min.js

jquery-migrate.min.js

164 ms

bundle.js

bundle.js

174 ms

v4-shims.min.js

v4-shims.min.js

174 ms

swap.js

swap.js

66 ms

FA__DOMContentLoadedEventDispatcher.js

FA__DOMContentLoadedEventDispatcher.js

50 ms

wforms-layout.css

wforms-layout.css

56 ms

theme-91.css

theme-91.css

51 ms

wforms.js

wforms.js

56 ms

localization-en_US.js

localization-en_US.js

53 ms

open-telemetry.e3e59835d0ec08f714f1.js

open-telemetry.e3e59835d0ec08f714f1.js

56 ms

post-8698.css

post-8698.css

188 ms

animations.min.css

animations.min.css

188 ms

geotarget-public.js

geotarget-public.js

195 ms

selectize.min.js

selectize.min.js

216 ms

rate-my-post.min.js

rate-my-post.min.js

376 ms

general.min.js

general.min.js

212 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

228 ms

imagesloaded.min.js

imagesloaded.min.js

236 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

240 ms

webpack.runtime.min.js

webpack.runtime.min.js

217 ms

frontend-modules.min.js

frontend-modules.min.js

218 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

222 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

331 ms

wp-polyfill.min.js

wp-polyfill.min.js

334 ms

hooks.min.js

hooks.min.js

313 ms

i18n.min.js

i18n.min.js

309 ms

frontend.min.js

frontend.min.js

369 ms

waypoints.min.js

waypoints.min.js

275 ms

core.min.js

core.min.js

274 ms

frontend.min.js

frontend.min.js

261 ms

elements-handlers.min.js

elements-handlers.min.js

260 ms

jquery.sticky.min.js

jquery.sticky.min.js

275 ms

gtm.js

gtm.js

177 ms

FOTF-Favicon-ormdhfl0vt3xv609ior9vvpmjd29zqifd80g2uei4a.png

FOTF-Favicon-ormdhfl0vt3xv609ior9vvpmjd29zqifd80g2uei4a.png

94 ms

hope-restored-header-logo-updated-2022-1024x207.png

hope-restored-header-logo-updated-2022-1024x207.png

96 ms

Nav-New-Banner.png

Nav-New-Banner.png

97 ms

MicrosoftTeams-image-3.jpg

MicrosoftTeams-image-3.jpg

99 ms

Hope-Restored-2020-32.jpg

Hope-Restored-2020-32.jpg

97 ms

HR-Home-pg-Testimonial-BG-rgj.jpg

HR-Home-pg-Testimonial-BG-rgj.jpg

152 ms

hope-restored-logo-footer-compressed-ormdhfl2a8p6osg4ly9si768adothhfn59yvtjy3jq.png

hope-restored-logo-footer-compressed-ormdhfl2a8p6osg4ly9si768adothhfn59yvtjy3jq.png

153 ms

fotf-footer-compressed-ormdhfl2db7p2hlsey83nml0j83c7amcz5peb5820m.png

fotf-footer-compressed-ormdhfl2db7p2hlsey83nml0j83c7amcz5peb5820m.png

151 ms

HopeRestored_Preferred_noMod_CP_RGB-300x92.png

HopeRestored_Preferred_noMod_CP_RGB-300x92.png

154 ms

css

css

23 ms

css2

css2

34 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

25 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

33 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

44 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

43 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

45 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

43 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

44 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

45 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

46 ms

S6u9w4BMUTPHh7USSwiPHA.ttf

S6u9w4BMUTPHh7USSwiPHA.ttf

73 ms

S6u8w4BMUTPHh30AXC-v.ttf

S6u8w4BMUTPHh30AXC-v.ttf

74 ms

fa-solid-900.woff

fa-solid-900.woff

169 ms

fa-regular-400.woff

fa-regular-400.woff

168 ms

eicons.woff

eicons.woff

248 ms

0QI6MX1D_JOuGQbT0gvTJPa787zAvBJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787zAvBJBkqg.ttf

75 ms

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqg.ttf

73 ms

0QI6MX1D_JOuGQbT0gvTJPa787wsuxJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787wsuxJBkqg.ttf

73 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqg.ttf

73 ms

wforms-jsonly.css

wforms-jsonly.css

15 ms

js

js

101 ms

destination

destination

100 ms

destination

destination

279 ms

bat.js

bat.js

352 ms

fbevents.js

fbevents.js

349 ms

w.js

w.js

350 ms

hotjar-708805.js

hotjar-708805.js

520 ms

45954263-b894-48fc-b0bb-40979513431a.js

45954263-b894-48fc-b0bb-40979513431a.js

378 ms

widget.js

widget.js

565 ms

c34ae8ab367b15d8

c34ae8ab367b15d8

156 ms

5257332.js

5257332.js

161 ms

ppas.js

ppas.js

80 ms

zcpt.js

zcpt.js

245 ms

218 ms

telemetry.js

telemetry.js

225 ms

up_loader.1.1.0.js

up_loader.1.1.0.js

181 ms

js

js

107 ms

js

js

98 ms

modules.4d9dd1518dc89987e57a.js

modules.4d9dd1518dc89987e57a.js

181 ms

ppms.php

ppms.php

106 ms

5257332

5257332

183 ms

widget_app_base_1715342638247.js

widget_app_base_1715342638247.js

119 ms

generic

generic

55 ms

trackpoint-async.js

trackpoint-async.js

87 ms

generic

generic

31 ms

settings.luckyorange.net

settings.luckyorange.net

41 ms

o8jPxregtN

o8jPxregtN

392 ms

89 ms

clarity.js

clarity.js

25 ms

17 ms

appnexus

appnexus

6 ms

pixel

pixel

28 ms

12 ms

46 ms

appnexus

appnexus

7 ms

pixels

pixels

55 ms

254 ms

pixel

pixel

18 ms

rubicon

rubicon

4 ms

google

google

4 ms

user-registering

user-registering

155 ms

match

match

20102 ms

click

click

367 ms

usermatch.gif

usermatch.gif

9 ms

Pug

Pug

155 ms

cs

cs

267 ms

um

um

196 ms

3838731841918866101

3838731841918866101

625 ms

199 ms

put

put

159 ms

29729

29729

512 ms

33302

33302

217 ms

match

match

115 ms

165 ms

67 ms

match

match

46 ms

match

match

23 ms

gdpr_consent=

gdpr_consent=

42 ms

xuid

xuid

10 ms

59 ms

tap.php

tap.php

9 ms

rum

rum

50 ms

match

match

48 ms

sd

sd

48 ms

pixel.gif

pixel.gif

161 ms

setuid

setuid

22 ms

en-US.json

en-US.json

12 ms

RX-ef4623e6-061e-420a-8aac-2a6e02a4f134-005

RX-ef4623e6-061e-420a-8aac-2a6e02a4f134-005

23 ms

info2

info2

34 ms

pixel

pixel

15 ms

11 ms

pixel.gif

pixel.gif

290 ms

p

p

69 ms

11 ms

3.gif

3.gif

93 ms

c.gif

c.gif

8 ms

Accessibility Review

nationalmarriage.com accessibility score

96

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

<frame> or <iframe> elements do not have a title

Best Practices

nationalmarriage.com 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

High

Page has valid source maps

SEO Factors

nationalmarriage.com SEO score

98

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

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 Nationalmarriage.com 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 Nationalmarriage.com 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

nationalmarriage.com

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