Tools & Wizards About Us
swag.buzz screenshot

Report Summary

  • 23

    Performance

    Renders faster than
    41% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

swag.buzz

Domain name swag.buzz in the RU-CENTER domain store

Page Load Speed

8.2 sec in total

First Response

3.2 sec

Resources Loaded

4.9 sec

Page Rendered

143 ms

swag.buzz screenshot

About Website

Visit swag.buzz now to see the best up-to-date Swag content and also check out these interesting facts you probably never knew about swag.buzz

Find out the cost of the swag.buzz domain, age, history of sites on the swag.buzz domain in the RU-CENTER domain name store.

Visit swag.buzz

Key Findings

We analyzed Swag.buzz page load time and found that the first response time was 3.2 sec and then it took 5.1 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

swag.buzz performance score

23

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.0 s

23/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value6,030 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value15.0 s

7/100

10%

Network Requests Diagram

swag.buzz

3154 ms

succeed.media

73 ms

app

96 ms

blue-geo.png

1017 ms

cloudflare.min.js

81 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Swag.buzz, 11% (5 requests) were made to Cdnjs.cloudflare.com and 11% (5 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (3.2 sec) belongs to the original domain Swag.buzz.

Page Optimization Overview & Recommendations

Page size can be reduced by 628.2 kB (51%)

Content Size

1.2 MB

After Optimization

609.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Swag.buzz main page is 1.2 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. 30% of websites need less resources to load. Javascripts take 849.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 46.0 kB

  • Original 58.5 kB
  • After minification 57.4 kB
  • After compression 12.5 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 46.0 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 983 B

  • Original 210.7 kB
  • After minification 209.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. Swag images are well optimized though.

JavaScript Optimization

-64%

Potential reduce by 542.9 kB

  • Original 849.9 kB
  • After minification 849.2 kB
  • After compression 307.0 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 542.9 kB or 64% of the original size.

CSS Optimization

-32%

Potential reduce by 38.3 kB

  • Original 118.4 kB
  • After minification 113.5 kB
  • After compression 80.1 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. Swag.buzz needs all CSS files to be minified and compressed as it can save up to 38.3 kB or 32% of the original size.

Requests Breakdown

Number of requests can be reduced by 29 (81%)

Requests Now

36

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

swag.buzz

swag.buzz

3154 ms

succeed.media

succeed.media

73 ms

app

app

96 ms

blue-geo.png

blue-geo.png

1017 ms

cloudflare.min.js

cloudflare.min.js

81 ms

lander.css

lander.css

110 ms

css

css

144 ms

font-awesome.css

font-awesome.css

128 ms

video-js.css

video-js.css

166 ms

mediaelement.min.js

mediaelement.min.js

126 ms

parsley.min.js

parsley.min.js

142 ms

ate.min.js

ate.min.js

410 ms

lander.js

lander.js

151 ms

mediaelementplayer.min.css

mediaelementplayer.min.css

143 ms

mejs-skins.css

mejs-skins.css

147 ms

cf_pe_orders-6bbca54c0b08197642654ca9fb45a7f3.js

cf_pe_orders-6bbca54c0b08197642654ca9fb45a7f3.js

350 ms

video.js

video.js

214 ms

garlic.cf.js

garlic.cf.js

33 ms

analytics.js

analytics.js

110 ms

jquery.min.js

jquery.min.js

8 ms

ga.js

ga.js

130 ms

coollogo_com-22837858.png

coollogo_com-22837858.png

164 ms

sdk.js

sdk.js

296 ms

closemodal.png

closemodal.png

359 ms

arrow.png

arrow.png

105 ms

DvlFBScY1r-FMtZSYIYoYw.ttf

DvlFBScY1r-FMtZSYIYoYw.ttf

102 ms

v0SdcGFAl2aezM9Vq_aFTQ.ttf

v0SdcGFAl2aezM9Vq_aFTQ.ttf

127 ms

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf

141 ms

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf

144 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

32 ms

collect

collect

30 ms

collect

collect

50 ms

__utm.gif

__utm.gif

34 ms

ate.min.js

ate.min.js

324 ms

133 ms

xd_arbiter.php

xd_arbiter.php

464 ms

__utm.gif

__utm.gif

145 ms

342 ms

iframe_api

iframe_api

113 ms

__utm.gif

__utm.gif

28 ms

285 ms

cf.js

cf.js

23 ms

www-widgetapi.js

www-widgetapi.js

62 ms

nr-686.min.js

nr-686.min.js

318 ms

track

track

203 ms

Accessibility Review

swag.buzz accessibility score

86

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

swag.buzz best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

swag.buzz SEO score

93

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

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 Swag.buzz 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 Swag.buzz 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

swag.buzz

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