Tools & Wizards About Us
significant1.com screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

significant1.com

One moment, please...

Page Load Speed

6.4 sec in total

First Response

826 ms

Resources Loaded

4.8 sec

Page Rendered

703 ms

significant1.com screenshot

About Website

Visit significant1.com now to see the best up-to-date Significant 1 content and also check out these interesting facts you probably never knew about significant1.com

International boutique matchmaking agency can help find for you elite singles in Canada and USA using the dating site in Calgary, Toronto, Montreal, Edmonton or in other provinces. Our matchmaking ser...

Visit significant1.com

Key Findings

We analyzed Significant1.com page load time and found that the first response time was 826 ms and then it took 5.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

significant1.com performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

7/100

10%

LCP (Largest Contentful Paint)

Value6.0 s

13/100

25%

SI (Speed Index)

Value10.0 s

9/100

10%

TBT (Total Blocking Time)

Value1,580 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value13.9 s

10/100

10%

Network Requests Diagram

significant1.com

826 ms

rst5jaz.css

216 ms

style.min.css

68 ms

styles.css

133 ms

theme.min.css

193 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 64% of them (36 requests) were addressed to the original Significant1.com, 9% (5 requests) were made to Youtube.com and 7% (4 requests) were made to Use.typekit.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Mc.yandex.ru.

Page Optimization Overview & Recommendations

Page size can be reduced by 474.5 kB (32%)

Content Size

1.5 MB

After Optimization

986.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Significant1.com main page is 1.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. 65% of websites need less resources to load. CSS take 532.7 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 76.2 kB

  • Original 96.0 kB
  • After minification 92.6 kB
  • After compression 19.8 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 76.2 kB or 79% of the original size.

Image Optimization

-10%

Potential reduce by 48.3 kB

  • Original 481.1 kB
  • After minification 432.8 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. Significant 1 images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.8 kB

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

CSS Optimization

-65%

Potential reduce by 347.2 kB

  • Original 532.7 kB
  • After minification 531.9 kB
  • After compression 185.5 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. Significant1.com needs all CSS files to be minified and compressed as it can save up to 347.2 kB or 65% of the original size.

Requests Breakdown

Number of requests can be reduced by 30 (63%)

Requests Now

48

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

significant1.com

significant1.com

826 ms

rst5jaz.css

rst5jaz.css

216 ms

style.min.css

style.min.css

68 ms

styles.css

styles.css

133 ms

theme.min.css

theme.min.css

193 ms

js_composer_front_custom.css

js_composer_front_custom.css

199 ms

ubermenu.min.css

ubermenu.min.css

191 ms

blackwhite2.css

blackwhite2.css

190 ms

font-awesome.min.css

font-awesome.min.css

194 ms

jquery.min.js

jquery.min.js

198 ms

jquery-migrate.min.js

jquery-migrate.min.js

320 ms

js

js

83 ms

font-awesome.min.css

font-awesome.min.css

336 ms

hooks.min.js

hooks.min.js

338 ms

i18n.min.js

i18n.min.js

337 ms

index.js

index.js

337 ms

index.js

index.js

337 ms

cf7-google-analytics.min.js

cf7-google-analytics.min.js

337 ms

theme.min.js

theme.min.js

432 ms

admin_bar_ajax.js

admin_bar_ajax.js

433 ms

api.js

api.js

46 ms

wp-polyfill.min.js

wp-polyfill.min.js

433 ms

index.js

index.js

432 ms

ubermenu.min.js

ubermenu.min.js

433 ms

js_composer_front.min.js

js_composer_front.min.js

443 ms

p.css

p.css

22 ms

tag.js

tag.js

1286 ms

jx_ibKOTNKo

jx_ibKOTNKo

238 ms

Sig1.png

Sig1.png

112 ms

Slider-Background.jpg

Slider-Background.jpg

194 ms

happy-couple-running-on-the-beach-1.jpg

happy-couple-running-on-the-beach-1.jpg

111 ms

for-him-professional-match-making-for-professional-men.jpg

for-him-professional-match-making-for-professional-men.jpg

111 ms

for-her-background-professional-match-making-for-woman.jpg

for-her-background-professional-match-making-for-woman.jpg

112 ms

saphire-package.png

saphire-package.png

195 ms

emeral-package.png

emeral-package.png

195 ms

ruby-package.png

ruby-package.png

193 ms

daimond-package.png

daimond-package.png

194 ms

number-1.png

number-1.png

196 ms

number-2.png

number-2.png

236 ms

number-3.png

number-3.png

239 ms

d

d

89 ms

d

d

90 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

206 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

196 ms

d

d

91 ms

www-player.css

www-player.css

16 ms

www-embed-player.js

www-embed-player.js

73 ms

base.js

base.js

129 ms

ad_status.js

ad_status.js

197 ms

FaW0q-y8JjmoU9T0UDvbGph-S7KEa5MvRd-6bYW3ujg.js

FaW0q-y8JjmoU9T0UDvbGph-S7KEa5MvRd-6bYW3ujg.js

100 ms

embed.js

embed.js

40 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

150 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

154 ms

Create

Create

29 ms

id

id

19 ms

GenerateIT

GenerateIT

21 ms

Accessibility Review

significant1.com accessibility score

89

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

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

Best Practices

significant1.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

significant1.com SEO score

92

Search Engine Optimization Advices

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 Significant1.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 Significant1.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

significant1.com

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