Tools & Wizards About Us
sweet.io screenshot

Report Summary

  • 58

    Performance

    Renders faster than
    74% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 0

    Best Practices

  • 95

    SEO

    Google-friendlier than
    90% of websites

sweet.io

Sweet | The Future for Global Sports IP

Page Load Speed

882 ms in total

First Response

61 ms

Resources Loaded

739 ms

Page Rendered

82 ms

sweet.io screenshot

About Website

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

Gamified blockchain digital collectible experiences driving fan engagement for the world's top sports organizations.

Visit sweet.io

Key Findings

We analyzed Sweet.io page load time and found that the first response time was 61 ms and then it took 821 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.

Performance Metrics

sweet.io performance score

58

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.8 s

89/100

10%

LCP (Largest Contentful Paint)

Value1.8 s

98/100

25%

SI (Speed Index)

Value4.4 s

73/100

10%

TBT (Total Blocking Time)

Value2,580 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value14.6 s

8/100

10%

Network Requests Diagram

sweet.io

61 ms

sweet.io

185 ms

ba1139214195694a.css

52 ms

polyfills-c67a75d1b6f99dc8.js

104 ms

osano.js

403 ms

Our browser made a total of 23 requests to load all elements on the main page. We found that 61% of them (14 requests) were addressed to the original Sweet.io, 22% (5 requests) were made to Use.typekit.net and 9% (2 requests) were made to Collectible.sweet.io. The less responsive or slowest element that took the longest time to load (403 ms) relates to the external source Cmp.osano.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 28.3 kB (77%)

Content Size

36.7 kB

After Optimization

8.3 kB

  • HTML
  • CSS

In fact, the total size of Sweet.io main page is 36.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. 30% of websites need less resources to load. HTML takes 36.7 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 28.3 kB

  • Original 36.7 kB
  • After minification 36.7 kB
  • After compression 8.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 28.3 kB or 77% of the original size.

CSS Optimization

-0%

Potential reduce by 0 B

  • Original 5 B

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.

Requests Breakdown

Number of requests can be reduced by 11 (69%)

Requests Now

16

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sweet.io

sweet.io

61 ms

sweet.io

sweet.io

185 ms

ba1139214195694a.css

ba1139214195694a.css

52 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

104 ms

osano.js

osano.js

403 ms

webpack-d59bb3ce070abc84.js

webpack-d59bb3ce070abc84.js

122 ms

framework-79bce4a3a540b080.js

framework-79bce4a3a540b080.js

128 ms

main-e726f5d3134a540b.js

main-e726f5d3134a540b.js

125 ms

_app-93d48d65010cdb8a.js

_app-93d48d65010cdb8a.js

273 ms

2279-0789bd5cd6031938.js

2279-0789bd5cd6031938.js

121 ms

8182-da64b84c1ed33416.js

8182-da64b84c1ed33416.js

168 ms

3884-3e2b1e9c3005a284.js

3884-3e2b1e9c3005a284.js

188 ms

index-cce983eafc7d2aec.js

index-cce983eafc7d2aec.js

189 ms

_buildManifest.js

_buildManifest.js

195 ms

_ssgManifest.js

_ssgManifest.js

194 ms

p.css

p.css

27 ms

sweet-logo.svg

sweet-logo.svg

90 ms

breakawayLogo.svg

breakawayLogo.svg

134 ms

d

d

21 ms

d

d

27 ms

d

d

33 ms

d

d

33 ms

d

d

34 ms

Accessibility Review

sweet.io accessibility score

98

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

Links do not have a discernible name

SEO Factors

sweet.io SEO score

95

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 Sweet.io 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 Sweet.io 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

sweet.io

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