Tools & Wizards About Us
simplemarriage.net screenshot

Report Summary

  • 48

    Performance

    Renders faster than
    67% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

simplemarriage.net

Home - Passionately Married

Page Load Speed

39.6 sec in total

First Response

1 sec

Resources Loaded

11.2 sec

Page Rendered

27.4 sec

simplemarriage.net screenshot

About Website

Welcome to simplemarriage.net homepage info - get ready to check Simplemarriage best content for United States right away, or after learning these important things about simplemarriage.net

Visit simplemarriage.net

Key Findings

We analyzed Simplemarriage.net page load time and found that the first response time was 1 sec and then it took 38.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

simplemarriage.net performance score

48

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

74/100

10%

LCP (Largest Contentful Paint)

Value11.5 s

0/100

25%

SI (Speed Index)

Value4.4 s

74/100

10%

TBT (Total Blocking Time)

Value220 ms

88/100

30%

CLS (Cumulative Layout Shift)

Value0.621

10/100

15%

TTI (Time to Interactive)

Value6.7 s

56/100

10%

Network Requests Diagram

simplemarriage.net

1022 ms

analytics.js

639 ms

wp-emoji-release.min.js

347 ms

icons.css

1270 ms

share.css

1611 ms

Our browser made a total of 63 requests to load all elements on the main page. We found that 87% of them (55 requests) were addressed to the original Simplemarriage.net, 2% (1 request) were made to Google-analytics.com and 2% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Simplemarriage.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.1 MB (17%)

Content Size

6.5 MB

After Optimization

5.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Simplemarriage.net main page is 6.5 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. 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. Images take 5.5 MB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 24.3 kB

  • Original 31.5 kB
  • After minification 31.4 kB
  • After compression 7.2 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 24.3 kB or 77% of the original size.

Image Optimization

-7%

Potential reduce by 393.8 kB

  • Original 5.5 MB
  • After minification 5.1 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. Simplemarriage images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 314.2 kB

  • Original 487.7 kB
  • After minification 446.2 kB
  • After compression 173.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 314.2 kB or 64% of the original size.

CSS Optimization

-72%

Potential reduce by 358.0 kB

  • Original 498.7 kB
  • After minification 433.0 kB
  • After compression 140.7 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. Simplemarriage.net needs all CSS files to be minified and compressed as it can save up to 358.0 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 48 (80%)

Requests Now

60

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

simplemarriage.net

simplemarriage.net

1022 ms

analytics.js

analytics.js

639 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

347 ms

icons.css

icons.css

1270 ms

share.css

share.css

1611 ms

genericons.css

genericons.css

1632 ms

style.css

style.css

1402 ms

front-end.css

front-end.css

1590 ms

bbpress.css

bbpress.css

1588 ms

reset.css

reset.css

1953 ms

lms-sidebar.css

lms-sidebar.css

1952 ms

style.min.css

style.min.css

2387 ms

dashicons.min.css

dashicons.min.css

2135 ms

theme.css

theme.css

2117 ms

lms-style.css

lms-style.css

1950 ms

css

css

2529 ms

checkout.css

checkout.css

2649 ms

style.css

style.css

2526 ms

style.css

style.css

2436 ms

admin.css

admin.css

2435 ms

editor.css

editor.css

2434 ms

style.css

style.css

2434 ms

style.css

style.css

2582 ms

style.css

style.css

2628 ms

jquery.js

jquery.js

2582 ms

jquery-migrate.min.js

jquery-migrate.min.js

2627 ms

jquery.sharrre.min.js

jquery.sharrre.min.js

2627 ms

front-end.js

front-end.js

2581 ms

abus_script.js

abus_script.js

3036 ms

jquery.cookie.js

jquery.cookie.js

3035 ms

frontend-min.js

frontend-min.js

3035 ms

jquery.fitvids.js

jquery.fitvids.js

3034 ms

tracking.min.js

tracking.min.js

2938 ms

responsive-menu.js

responsive-menu.js

2938 ms

checkout-form.js

checkout-form.js

3353 ms

svgxuse.js

svgxuse.js

3061 ms

parallax.js

parallax.js

3061 ms

player.js

player.js

3061 ms

css.php

css.php

3299 ms

simplemarriage.net

simplemarriage.net

3204 ms

editor.js

editor.js

2262 ms

collect

collect

1773 ms

premise-zero-spam.js

premise-zero-spam.js

1921 ms

zero-spam.min.js

zero-spam.min.js

1900 ms

lms-navigation-module.js

lms-navigation-module.js

1959 ms

rm-automation-ajax.js

rm-automation-ajax.js

1957 ms

automation-formulas.js

automation-formulas.js

1820 ms

spui.fitvids.js

spui.fitvids.js

1595 ms

comment-reply.min.js

comment-reply.min.js

2046 ms

jquery.flexslider.js

jquery.flexslider.js

2082 ms

logo-white.png

logo-white.png

2848 ms

hometop2.jpg

hometop2.jpg

3112 ms

CoupleBed2copy.jpg

CoupleBed2copy.jpg

2803 ms

smr550logo.png

smr550logo.png

2798 ms

NakedMarriageAD2.jpeg

NakedMarriageAD2.jpeg

2765 ms

bg-5-copy.jpg

bg-5-copy.jpg

2839 ms

symbol-defs.svg

symbol-defs.svg

2766 ms

zhcz-_WihjSQC0oHJ9TCYL3hpw3pgy2gAi-Ip7WPMi0.woff

zhcz-_WihjSQC0oHJ9TCYL3hpw3pgy2gAi-Ip7WPMi0.woff

1916 ms

6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==

6nvU963vW96zvuZHXyGvkNfLa8try2vLa8try2vLa8try2vLaPbzi90vRj6IfRT+KfhS9KHpR9KLoRdGLohdFL4peFL0oelH0ouhF0YuiF0Uvil4UvSh6UfSi6EXRi6IXRS+KXhS9KHpR9KHoQ9GHog9FH4o+FD0oelD0oOToN3TgiAFDRg4b9C8VmLmgAAAAAVWwJZkAAA==

69 ms

quant.js

quant.js

1435 ms

admin-ajax.php

admin-ajax.php

1380 ms

rules-p-2cTwljkbMv6QM.js

rules-p-2cTwljkbMv6QM.js

265 ms

pixel;r=14291757;rf=0;a=p-2cTwljkbMv6QM;url=https%3A%2F%2Fsimplemarriage.net%2F;fpan=1;fpa=P0-1473781576-1504630483289;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504630483289;tzo=-180;ogl=locale.en_US%2Ctype.website%2Ctitle.-%20Simple%20Marriage%20-%2Curl.https%3A%2F%2Fsimplemarriage%252Enet%2F%2Csite_name.Simple%20Marriage

pixel;r=14291757;rf=0;a=p-2cTwljkbMv6QM;url=https%3A%2F%2Fsimplemarriage.net%2F;fpan=1;fpa=P0-1473781576-1504630483289;ns=0;ce=1;cm=;ref=;je=0;sr=1024x768x32;enc=n;dst=0;et=1504630483289;tzo=-180;ogl=locale.en_US%2Ctype.website%2Ctitle.-%20Simple%20Marriage%20-%2Curl.https%3A%2F%2Fsimplemarriage%252Enet%2F%2Csite_name.Simple%20Marriage

623 ms

Accessibility Review

simplemarriage.net accessibility score

86

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

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

SEO Factors

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

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

simplemarriage.net

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