Tools & Wizards About Us
wasp.love screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 82

    SEO

    Google-friendlier than
    44% of websites

wasp.love

WASP Love

Page Load Speed

1.6 sec in total

First Response

244 ms

Resources Loaded

1.2 sec

Page Rendered

187 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

Visit wasp.love

Key Findings

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

Performance Metrics

wasp.love performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value9.3 s

1/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value30 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.079

94/100

15%

TTI (Time to Interactive)

Value8.1 s

42/100

10%

Network Requests Diagram

wasp.love

244 ms

style.min.css

131 ms

bbpress.min.css

134 ms

mentions.min.css

138 ms

bp-tooltips.min.css

136 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 63.7 kB (8%)

Content Size

799.1 kB

After Optimization

735.3 kB

  • HTML
  • Images
  • CSS

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

HTML Optimization

-81%

Potential reduce by 53.5 kB

  • Original 66.1 kB
  • After minification 65.0 kB
  • After compression 12.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 53.5 kB or 81% of the original size.

Image Optimization

-1%

Potential reduce by 5.3 kB

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

CSS Optimization

-4%

Potential reduce by 4.9 kB

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

Requests Breakdown

Number of requests can be reduced by 45 (85%)

Requests Now

53

After Optimization

8

  • Images
  • JavaScript
  • CSS

The browser has sent 53 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 31 to 1 for JavaScripts and from 16 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

wasp.love

wasp.love

244 ms

style.min.css

style.min.css

131 ms

bbpress.min.css

bbpress.min.css

134 ms

mentions.min.css

mentions.min.css

138 ms

bp-tooltips.min.css

bp-tooltips.min.css

136 ms

widgets-legacy.css

widgets-legacy.css

136 ms

wpa.css

wpa.css

134 ms

wp-ulike.min.css

wp-ulike.min.css

193 ms

style.css

style.css

268 ms

css

css

20 ms

font-awesome.css

font-awesome.css

196 ms

widget.css

widget.css

202 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

201 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

198 ms

dashicons.min.css

dashicons.min.css

322 ms

rtmedia.min.css

rtmedia.min.css

263 ms

rtm-upload-terms.min.css

rtm-upload-terms.min.css

261 ms

moxie.min.js

moxie.min.js

335 ms

plupload.min.js

plupload.min.js

273 ms

jquery.min.js

jquery.min.js

396 ms

jquery-migrate.min.js

jquery-migrate.min.js

330 ms

wp-embed.min.js

wp-embed.min.js

330 ms

buddypress-activity-filter-public.js

buddypress-activity-filter-public.js

331 ms

login-with-ajax.legacy.min.js

login-with-ajax.legacy.min.js

386 ms

ajaxify.min.js

ajaxify.min.js

391 ms

wp-power-stats.js

wp-power-stats.js

393 ms

underscore.min.js

underscore.min.js

494 ms

backbone.min.js

backbone.min.js

494 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

495 ms

emoji-picker.js

emoji-picker.js

496 ms

rtmedia.min.js

rtmedia.min.js

496 ms

rtMedia.backbone.js

rtMedia.backbone.js

496 ms

jquery.caret.min.js

jquery.caret.min.js

496 ms

jquery.atwho.min.js

jquery.atwho.min.js

497 ms

mentions.min.js

mentions.min.js

515 ms

wpa.js

wpa.js

520 ms

wp-ulike.min.js

wp-ulike.min.js

522 ms

tracker.js

tracker.js

474 ms

bootstrap.min.js

bootstrap.min.js

404 ms

fillsize.js

fillsize.js

404 ms

jquery.arctext.js

jquery.arctext.js

472 ms

theme.js

theme.js

474 ms

buddypress-edit-activity.min.js

buddypress-edit-activity.min.js

470 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

540 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

408 ms

imagesloaded.min.js

imagesloaded.min.js

438 ms

masonry.min.js

masonry.min.js

469 ms

jquery.masonry.min.js

jquery.masonry.min.js

471 ms

cropped-pairs-1779065.jpg

cropped-pairs-1779065.jpg

576 ms

love-rejoices-truth-150x150.jpg

love-rejoices-truth-150x150.jpg

360 ms

like.svg

like.svg

256 ms

love-procreate-150x150.jpg

love-procreate-150x150.jpg

301 ms

wasp-love-1-150x150.png

wasp-love-1-150x150.png

384 ms

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

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

322 ms

font

font

84 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

316 ms

font

font

91 ms

font

font

118 ms

Accessibility Review

wasp.love accessibility score

86

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

67

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

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

wasp.love SEO score

82

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