Tools & Wizards About Us
significant1.com screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

significant1.com

Professional Matchmaking Service Company - Significant1

Page Load Speed

6.2 sec in total

First Response

797 ms

Resources Loaded

4.9 sec

Page Rendered

502 ms

significant1.com screenshot

About Website

Visit significant1.com now to see the best up-to-date Significant1 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 797 ms and then it took 5.4 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

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value6.3 s

11/100

25%

SI (Speed Index)

Value8.8 s

15/100

10%

TBT (Total Blocking Time)

Value2,420 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.156

74/100

15%

TTI (Time to Interactive)

Value14.1 s

10/100

10%

Network Requests Diagram

significant1.com

797 ms

rst5jaz.css

73 ms

style.min.css

56 ms

styles.css

116 ms

theme.min.css

165 ms

Our browser made a total of 58 requests to load all elements on the main page. We found that 62% 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 107.9 kB (10%)

Content Size

1.1 MB

After Optimization

948.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Significant1.com main page is 1.1 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. Javascripts take 564.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 75.2 kB

  • Original 94.9 kB
  • After minification 91.5 kB
  • After compression 19.7 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 75.2 kB or 79% of the original size.

Image Optimization

-12%

Potential reduce by 25.1 kB

  • Original 211.4 kB
  • After minification 186.3 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, Significant1 needs image optimization as it can save up to 25.1 kB or 12% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-1%

Potential reduce by 3.9 kB

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

CSS Optimization

-2%

Potential reduce by 3.8 kB

  • Original 185.2 kB
  • After minification 185.2 kB
  • After compression 181.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 has all CSS files already compressed.

Requests Breakdown

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

Requests Now

50

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Significant1. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 22 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

797 ms

rst5jaz.css

rst5jaz.css

73 ms

style.min.css

style.min.css

56 ms

styles.css

styles.css

116 ms

theme.min.css

theme.min.css

165 ms

js_composer_front_custom.css

js_composer_front_custom.css

194 ms

ubermenu.min.css

ubermenu.min.css

191 ms

blackwhite2.css

blackwhite2.css

185 ms

font-awesome.min.css

font-awesome.min.css

187 ms

jquery.min.js

jquery.min.js

235 ms

jquery-migrate.min.js

jquery-migrate.min.js

249 ms

js

js

70 ms

font-awesome.min.css

font-awesome.min.css

278 ms

index.js

index.js

277 ms

index.js

index.js

276 ms

cf7-google-analytics.min.js

cf7-google-analytics.min.js

278 ms

theme.min.js

theme.min.js

279 ms

admin_bar_ajax.js

admin_bar_ajax.js

418 ms

api.js

api.js

40 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

419 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

418 ms

wp-polyfill.min.js

wp-polyfill.min.js

420 ms

index.js

index.js

419 ms

ubermenu.min.js

ubermenu.min.js

419 ms

js_composer_front.min.js

js_composer_front.min.js

488 ms

p.css

p.css

34 ms

tag.js

tag.js

1310 ms

jx_ibKOTNKo

jx_ibKOTNKo

308 ms

Sig1.png

Sig1.png

221 ms

Slider-Background.jpg

Slider-Background.jpg

464 ms

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

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

219 ms

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

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

218 ms

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

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

219 ms

saphire-package.png

saphire-package.png

223 ms

emeral-package.png

emeral-package.png

221 ms

ruby-package.png

ruby-package.png

220 ms

daimond-package.png

daimond-package.png

221 ms

number-1.png

number-1.png

273 ms

number-2.png

number-2.png

303 ms

number-3.png

number-3.png

304 ms

d

d

82 ms

d

d

193 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

239 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

689 ms

d

d

238 ms

www-player.css

www-player.css

174 ms

www-embed-player.js

www-embed-player.js

204 ms

base.js

base.js

322 ms

recaptcha__en.js

recaptcha__en.js

198 ms

ad_status.js

ad_status.js

321 ms

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

6mt_jkCC8QEMfVv4UaXe0WVRezbgElH9_VSMBGBwk28.js

187 ms

embed.js

embed.js

108 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

153 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

154 ms

advert.gif

advert.gif

505 ms

id

id

145 ms

Create

Create

29 ms

GenerateIT

GenerateIT

13 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

83

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

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 Significant1. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: