Tools & Wizards About Us
wasp.love screenshot

Report Summary

  • 18

    Performance

    Renders faster than
    34% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 60% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

wasp.love

WASP Love

Page Load Speed

2.8 sec in total

First Response

509 ms

Resources Loaded

2 sec

Page Rendered

324 ms

wasp.love screenshot

About Website

Visit wasp.love now to see the best up-to-date WASP content for United States and also check out these interesting facts you probably never knew about wasp.love

Dating - Reformed Christian, Quiverfull, Confederate, Homeschooled, Christian Identity, white nationalism, altright, Sovereign Grace Singles

Visit wasp.love

Key Findings

We analyzed Wasp.love page load time and found that the first response time was 509 ms and then it took 2.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

wasp.love performance score

18

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.0 s

1/100

10%

LCP (Largest Contentful Paint)

Value12.6 s

0/100

25%

SI (Speed Index)

Value12.2 s

3/100

10%

TBT (Total Blocking Time)

Value1,420 ms

15/100

30%

CLS (Cumulative Layout Shift)

Value0.135

80/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

wasp.love

509 ms

wp-emoji-release.min.js

80 ms

style.min.css

155 ms

login-form.min.css

151 ms

member.min.css

151 ms

Our browser made a total of 74 requests to load all elements on the main page. We found that 93% of them (69 requests) were addressed to the original Wasp.love, 5% (4 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (826 ms) belongs to the original domain Wasp.love.

Page Optimization Overview & Recommendations

Page size can be reduced by 123.4 kB (18%)

Content Size

668.7 kB

After Optimization

545.3 kB

  • HTML
  • Images
  • CSS

In fact, the total size of Wasp.love main page is 668.7 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. 60% of websites need less resources to load. Images take 421.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 40.0 kB

  • Original 50.6 kB
  • After minification 49.3 kB
  • After compression 10.6 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 40.0 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 421.9 kB
  • After minification 421.9 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. WASP images are well optimized though.

CSS Optimization

-42%

Potential reduce by 83.4 kB

  • Original 196.2 kB
  • After minification 196.0 kB
  • After compression 112.8 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. Wasp.love needs all CSS files to be minified and compressed as it can save up to 83.4 kB or 42% of the original size.

Requests Breakdown

Number of requests can be reduced by 59 (95%)

Requests Now

62

After Optimization

3

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

wasp.love

wasp.love

509 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

80 ms

style.min.css

style.min.css

155 ms

login-form.min.css

login-form.min.css

151 ms

member.min.css

member.min.css

151 ms

members.min.css

members.min.css

146 ms

dynamic-members.min.css

dynamic-members.min.css

146 ms

latest-activities.min.css

latest-activities.min.css

147 ms

friends.min.css

friends.min.css

209 ms

group.min.css

group.min.css

207 ms

groups.min.css

groups.min.css

210 ms

dynamic-groups.min.css

dynamic-groups.min.css

206 ms

sitewide-notices.min.css

sitewide-notices.min.css

202 ms

bbpress.min.css

bbpress.min.css

212 ms

mentions.min.css

mentions.min.css

269 ms

buddypress.min.css

buddypress.min.css

277 ms

wpa.css

wpa.css

275 ms

wp-ulike.min.css

wp-ulike.min.css

272 ms

style.css

style.css

348 ms

css

css

41 ms

font-awesome.css

font-awesome.css

288 ms

widget.css

widget.css

338 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

343 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

333 ms

dashicons.min.css

dashicons.min.css

476 ms

rtmedia.min.css

rtmedia.min.css

405 ms

rtm-upload-terms.min.css

rtm-upload-terms.min.css

409 ms

moxie.min.js

moxie.min.js

513 ms

plupload.min.js

plupload.min.js

508 ms

jquery.min.js

jquery.min.js

509 ms

jquery-migrate.min.js

jquery-migrate.min.js

510 ms

confirm.min.js

confirm.min.js

509 ms

widget-members.min.js

widget-members.min.js

510 ms

jquery-query.min.js

jquery-query.min.js

509 ms

jquery-cookie.min.js

jquery-cookie.min.js

768 ms

jquery-scroll-to.min.js

jquery-scroll-to.min.js

760 ms

buddypress.min.js

buddypress.min.js

762 ms

widget-friends.min.js

widget-friends.min.js

760 ms

buddypress-activity-filter-public.js

buddypress-activity-filter-public.js

748 ms

login-with-ajax.legacy.min.js

login-with-ajax.legacy.min.js

702 ms

wp-power-stats.js

wp-power-stats.js

826 ms

underscore.min.js

underscore.min.js

821 ms

backbone.min.js

backbone.min.js

823 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

820 ms

rtmedia.min.js

rtmedia.min.js

820 ms

rtMedia.backbone.js

rtMedia.backbone.js

759 ms

jquery.caret.min.js

jquery.caret.min.js

760 ms

jquery.atwho.min.js

jquery.atwho.min.js

759 ms

mentions.min.js

mentions.min.js

759 ms

wpa.js

wpa.js

776 ms

wp-ulike.min.js

wp-ulike.min.js

765 ms

wp-embed.min.js

wp-embed.min.js

710 ms

bootstrap.min.js

bootstrap.min.js

703 ms

fillsize.js

fillsize.js

698 ms

jquery.arctext.js

jquery.arctext.js

692 ms

theme.js

theme.js

686 ms

buddypress-edit-activity.min.js

buddypress-edit-activity.min.js

639 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

763 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

759 ms

imagesloaded.min.js

imagesloaded.min.js

694 ms

masonry.min.js

masonry.min.js

623 ms

jquery.masonry.min.js

jquery.masonry.min.js

624 ms

hit

hit

497 ms

cropped-bride-1867228.jpg

cropped-bride-1867228.jpg

579 ms

love-rejoices-truth-150x150.jpg

love-rejoices-truth-150x150.jpg

381 ms

love-procreate-150x150.jpg

love-procreate-150x150.jpg

374 ms

wasp-love-1-150x150.png

wasp-love-1-150x150.png

373 ms

food-couple-sweet-married-150x150.jpg

food-couple-sweet-married-150x150.jpg

374 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

164 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

164 ms

46kulbz5WjvLqJZVam_k.ttf

46kulbz5WjvLqJZVam_k.ttf

165 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

207 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

167 ms

admin-ajax.php

admin-ajax.php

241 ms

Accessibility Review

wasp.love accessibility score

85

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.

Best Practices

wasp.love best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

wasp.love 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 Wasp.love 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 Wasp.love 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

wasp.love

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