Tools & Wizards About Us
sweary.com screenshot

Report Summary

  • 56

    Performance

    Renders faster than
    72% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

sweary.com

Insult Generator: WARNING! - You WILL Laugh with sweary.com

Page Load Speed

1.7 sec in total

First Response

140 ms

Resources Loaded

1.2 sec

Page Rendered

390 ms

sweary.com screenshot

About Website

Click here to check amazing Sweary content. Otherwise, check out these important facts you probably never knew about sweary.com

Click Now, You Will Laugh! Generate insults with sweary.com - impress your friends & offend your relatives Now with this free random insult generator!

Visit sweary.com

Key Findings

We analyzed Sweary.com page load time and found that the first response time was 140 ms and then it took 1.6 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

sweary.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.9 s

88/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value4.7 s

69/100

10%

TBT (Total Blocking Time)

Value3,690 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value11.6 s

18/100

10%

Network Requests Diagram

sweary.com

140 ms

cloudflare.min.js

13 ms

bootstrap.min.css

7 ms

css

32 ms

font-awesome.min.css

10 ms

Our browser made a total of 42 requests to load all elements on the main page. We found that 24% of them (10 requests) were addressed to the original Sweary.com, 17% (7 requests) were made to Tpc.googlesyndication.com and 14% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (545 ms) relates to the external source Googleads.g.doubleclick.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 264.7 kB (62%)

Content Size

424.2 kB

After Optimization

159.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sweary.com main page is 424.2 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. CSS take 207.6 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 19.8 kB

  • Original 27.1 kB
  • After minification 27.0 kB
  • After compression 7.3 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 19.8 kB or 73% of the original size.

Image Optimization

-1%

Potential reduce by 1.0 kB

  • Original 71.2 kB
  • After minification 70.1 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. Sweary images are well optimized though.

JavaScript Optimization

-56%

Potential reduce by 66.4 kB

  • Original 118.2 kB
  • After minification 118.1 kB
  • After compression 51.8 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 66.4 kB or 56% of the original size.

CSS Optimization

-85%

Potential reduce by 177.4 kB

  • Original 207.6 kB
  • After minification 206.1 kB
  • After compression 30.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. Sweary.com needs all CSS files to be minified and compressed as it can save up to 177.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 18 (51%)

Requests Now

35

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sweary.com

sweary.com

140 ms

cloudflare.min.js

cloudflare.min.js

13 ms

bootstrap.min.css

bootstrap.min.css

7 ms

css

css

32 ms

font-awesome.min.css

font-awesome.min.css

10 ms

animate.min.css

animate.min.css

11 ms

creative.css

creative.css

9 ms

rocket.js

rocket.js

6 ms

header.jpg

header.jpg

7 ms

fb_share.jpg

fb_share.jpg

10 ms

bag2

bag2

72 ms

sdk.js

sdk.js

345 ms

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

k3k702ZOKiLJc3WVjuplzHhCUOGz7vYGh680lGh-uXM.woff

138 ms

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

EInbV5DfGHOiMmvb1Xr-hnhCUOGz7vYGh680lGh-uXM.woff

139 ms

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

MTP_ySUJH_bn48VBG8sNSnhCUOGz7vYGh680lGh-uXM.woff

138 ms

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

cJZKeOuBrn4kERxqtaUH3T8E0i7KZn-EPnyo3HZu7kw.woff

138 ms

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

DXI1ORHCpsQm3Vp6mXoaTXhCUOGz7vYGh680lGh-uXM.woff

138 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

139 ms

ca-pub-0330023364380707.js

ca-pub-0330023364380707.js

239 ms

zrt_lookup.html

zrt_lookup.html

228 ms

show_ads_impl.js

show_ads_impl.js

131 ms

analytics.js

analytics.js

39 ms

ads

ads

545 ms

collect

collect

26 ms

osd.js

osd.js

23 ms

ads

ads

137 ms

ads

ads

307 ms

ads

ads

185 ms

57 ms

xd_arbiter.php

xd_arbiter.php

258 ms

xd_arbiter.php

xd_arbiter.php

475 ms

abg.js

abg.js

48 ms

000000_new_ico.gif

000000_new_ico.gif

62 ms

m_js_controller.js

m_js_controller.js

14 ms

favicon

favicon

95 ms

s

s

68 ms

googlelogo_color_112x36dp.png

googlelogo_color_112x36dp.png

83 ms

nessie_icon_tiamat_white.png

nessie_icon_tiamat_white.png

63 ms

x_button_blue2.png

x_button_blue2.png

63 ms

5725240187735599819

5725240187735599819

31 ms

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

fBnyGA8Aionz5086-mElmoOSPUuyQ1M9Un647_EjucU.js

13 ms

5013680669448859142

5013680669448859142

24 ms

Accessibility Review

sweary.com accessibility score

81

Accessibility Issues

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-*] attributes do not match their roles

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Best Practices

sweary.com best practices score

75

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

Page has valid source maps

SEO Factors

sweary.com SEO score

100

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

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

sweary.com

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