Tools & Wizards About Us
tcr-mn.org screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

tcr-mn.org

Twin Cities Retrouvaille Marriage Help | Twin Cities Retrouvaille

Page Load Speed

5.5 sec in total

First Response

1.5 sec

Resources Loaded

3.7 sec

Page Rendered

334 ms

tcr-mn.org screenshot

About Website

Click here to check amazing Tcr Mn content. Otherwise, check out these important facts you probably never knew about tcr-mn.org

Through Retrouvaille, a rewarding marriage is out there for you, despite the pain and struggles you may be facing right now.

Visit tcr-mn.org

Key Findings

We analyzed Tcr-mn.org page load time and found that the first response time was 1.5 sec and then it took 4.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

tcr-mn.org performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value18.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value29.4 s

0/100

25%

SI (Speed Index)

Value27.5 s

0/100

10%

TBT (Total Blocking Time)

Value3,670 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.02

100/100

15%

TTI (Time to Interactive)

Value48.1 s

0/100

10%

Network Requests Diagram

www.tcr-mn.org

1476 ms

trx_addons_icons.css

79 ms

stylesheet.css

99 ms

stylesheet.css

101 ms

fontello.css

134 ms

Our browser made a total of 82 requests to load all elements on the main page. We found that 98% of them (80 requests) were addressed to the original Tcr-mn.org, 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Tcr-mn.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 4.3 MB (71%)

Content Size

6.0 MB

After Optimization

1.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Tcr-mn.org main page is 6.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. 75% 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. CSS take 3.0 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 148.8 kB

  • Original 177.0 kB
  • After minification 172.8 kB
  • After compression 28.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 148.8 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 28.7 kB

  • Original 887.2 kB
  • After minification 858.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. Tcr Mn images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 1.4 MB

  • Original 2.0 MB
  • After minification 1.9 MB
  • After compression 517.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 1.4 MB or 74% of the original size.

CSS Optimization

-88%

Potential reduce by 2.7 MB

  • Original 3.0 MB
  • After minification 2.9 MB
  • After compression 350.1 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. Tcr-mn.org needs all CSS files to be minified and compressed as it can save up to 2.7 MB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 65 (88%)

Requests Now

74

After Optimization

9

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.tcr-mn.org

www.tcr-mn.org

1476 ms

trx_addons_icons.css

trx_addons_icons.css

79 ms

stylesheet.css

stylesheet.css

99 ms

stylesheet.css

stylesheet.css

101 ms

fontello.css

fontello.css

134 ms

tribe-events-pro-mini-calendar-block.min.css

tribe-events-pro-mini-calendar-block.min.css

137 ms

advanced-popups-public.css

advanced-popups-public.css

150 ms

styles.css

styles.css

140 ms

magnific-popup.min.css

magnific-popup.min.css

145 ms

tribe-events-single-skeleton.min.css

tribe-events-single-skeleton.min.css

150 ms

tribe-events-single-full.min.css

tribe-events-single-full.min.css

176 ms

widget-base.min.css

widget-base.min.css

169 ms

style.css

style.css

176 ms

__styles-full.css

__styles-full.css

369 ms

trx_addons.animations.css

trx_addons.animations.css

251 ms

elementor-icons.min.css

elementor-icons.min.css

198 ms

frontend.min.css

frontend.min.css

263 ms

swiper.min.css

swiper.min.css

222 ms

e-swiper.min.css

e-swiper.min.css

214 ms

widget-spacer.min.css

widget-spacer.min.css

233 ms

widget-image.min.css

widget-image.min.css

254 ms

widget-text-editor.min.css

widget-text-editor.min.css

260 ms

widget-video.min.css

widget-video.min.css

272 ms

gutenberg.min.css

gutenberg.min.css

289 ms

front.css

front.css

305 ms

css

css

29 ms

rs6.css

rs6.css

338 ms

variables-skeleton.min.css

variables-skeleton.min.css

298 ms

variables-full.min.css

variables-full.min.css

305 ms

events-virtual-single-block.min.css

events-virtual-single-block.min.css

324 ms

style.css

style.css

336 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

344 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

343 ms

style.css

style.css

495 ms

__plugins-full.css

__plugins-full.css

536 ms

__custom.css

__custom.css

402 ms

style.css

style.css

388 ms

css

css

47 ms

fontawesome.min.css

fontawesome.min.css

394 ms

regular.min.css

regular.min.css

333 ms

jquery.min.js

jquery.min.js

390 ms

jquery-migrate.min.js

jquery-migrate.min.js

350 ms

advanced-popups-public.js

advanced-popups-public.js

318 ms

hooks.min.js

hooks.min.js

323 ms

i18n.min.js

i18n.min.js

351 ms

index.js

index.js

372 ms

index.js

index.js

347 ms

rbtools.min.js

rbtools.min.js

510 ms

rs6.min.js

rs6.min.js

492 ms

jquery.magnific-popup.min.js

jquery.magnific-popup.min.js

362 ms

__scripts-full.js

__scripts-full.js

483 ms

chart-legacy.min.js

chart-legacy.min.js

460 ms

superfish.min.js

superfish.min.js

444 ms

swiper.min.js

swiper.min.js

436 ms

gsap.min.js

gsap.min.js

427 ms

gutenberg.min.js

gutenberg.min.js

406 ms

front.min.js

front.min.js

407 ms

__scripts-full.js

__scripts-full.js

396 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

398 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

389 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

371 ms

skin.js

skin.js

362 ms

webpack.runtime.min.js

webpack.runtime.min.js

355 ms

frontend-modules.min.js

frontend-modules.min.js

381 ms

core.min.js

core.min.js

362 ms

frontend.min.js

frontend.min.js

352 ms

TCR_Logo_Color_30-792x273-1.png

TCR_Logo_Color_30-792x273-1.png

99 ms

dummy.png

dummy.png

71 ms

low_ap02801.jpg

low_ap02801.jpg

97 ms

holding_hands_resized.jpg

holding_hands_resized.jpg

99 ms

favico-512-nocopyright.jpg

favico-512-nocopyright.jpg

99 ms

writing-size_25-890x648.jpg

writing-size_25-890x648.jpg

227 ms

holding_hands-size_25-resized-890x648.jpg

holding_hands-size_25-resized-890x648.jpg

224 ms

TeXGyreTermes-Regular.woff

TeXGyreTermes-Regular.woff

182 ms

TeXGyreTermes-Bold.woff

TeXGyreTermes-Bold.woff

183 ms

fontello.woff

fontello.woff

184 ms

Aller.woff

Aller.woff

183 ms

Aller-Light.woff

Aller-Light.woff

184 ms

Aller-Bold.woff

Aller-Bold.woff

184 ms

fa-regular-400.woff

fa-regular-400.woff

128 ms

__responsive-full.css

__responsive-full.css

245 ms

__responsive-full.css

__responsive-full.css

104 ms

Accessibility Review

tcr-mn.org accessibility score

84

Accessibility Issues

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

High

Some elements have a [tabindex] value greater than 0

Best Practices

tcr-mn.org 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

tcr-mn.org SEO score

75

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 Tcr-mn.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 Tcr-mn.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

tcr-mn.org

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