Tools & Wizards About Us
sweetpee.com screenshot

Report Summary

  • 8

    Performance

    Renders faster than
    22% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

sweetpee.com

Best Premium Synthetic Urine and THC Detox Products for 2022 |TestNegative.com

Page Load Speed

2.2 sec in total

First Response

16 ms

Resources Loaded

1.4 sec

Page Rendered

744 ms

sweetpee.com screenshot

About Website

Visit sweetpee.com now to see the best up-to-date Sweetpee content and also check out these interesting facts you probably never knew about sweetpee.com

Since 1993, several million Clear Choice products have been sold to satisfied customers throughout the US, Canada, and Europe. Clear Choice™ The brand you can truly rely on!

Visit sweetpee.com

Key Findings

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

sweetpee.com performance score

8

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.2 s

0/100

25%

SI (Speed Index)

Value17.1 s

0/100

10%

TBT (Total Blocking Time)

Value8,320 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.228

55/100

15%

TTI (Time to Interactive)

Value29.4 s

0/100

10%

Network Requests Diagram

sweetpee.com

16 ms

testnegative.com

96 ms

358dd52ba8cdf2fa3de2d3635a110521.min.css

26 ms

styles-l.min.css

55 ms

e41b3d63558ccbb2d37b3c45fb457a93.min.js

107 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Sweetpee.com, 63% (34 requests) were made to Testnegative.com and 22% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (670 ms) relates to the external source Static.klaviyo.com.

Page Optimization Overview & Recommendations

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

Content Size

1.2 MB

After Optimization

957.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sweetpee.com 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 800.5 kB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 214.1 kB

  • Original 238.1 kB
  • After minification 167.1 kB
  • After compression 24.0 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. This page needs HTML code to be minified as it can gain 71.0 kB, which is 30% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 214.1 kB or 90% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

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

JavaScript Optimization

-1%

Potential reduce by 28 B

  • Original 4.1 kB
  • After minification 4.1 kB
  • After compression 4.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 64 B

  • Original 128.5 kB
  • After minification 128.5 kB
  • After compression 128.4 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. Sweetpee.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 14 (44%)

Requests Now

32

After Optimization

18

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sweetpee.com

sweetpee.com

16 ms

testnegative.com

testnegative.com

96 ms

358dd52ba8cdf2fa3de2d3635a110521.min.css

358dd52ba8cdf2fa3de2d3635a110521.min.css

26 ms

styles-l.min.css

styles-l.min.css

55 ms

e41b3d63558ccbb2d37b3c45fb457a93.min.js

e41b3d63558ccbb2d37b3c45fb457a93.min.js

107 ms

requirejs-config.min.js

requirejs-config.min.js

69 ms

css

css

91 ms

8518.js

8518.js

87 ms

css2

css2

191 ms

css2

css2

191 ms

css2

css2

191 ms

klaviyo.js

klaviyo.js

670 ms

default_0.js

default_0.js

69 ms

default_0_addition.js

default_0_addition.js

69 ms

print.min.css

print.min.css

245 ms

fbevents.js

fbevents.js

478 ms

LEGENDS_logo.svg

LEGENDS_logo.svg

414 ms

select-bg.svg

select-bg.svg

415 ms

TN_-_NEW_FREE_SHIPPING_MOBILE_012624.jpg

TN_-_NEW_FREE_SHIPPING_MOBILE_012624.jpg

412 ms

TN_4X3_MOBILE_160724.jpg

TN_4X3_MOBILE_160724.jpg

411 ms

home-slider-1c.webp

home-slider-1c.webp

427 ms

home-slider-2c.webp

home-slider-2c.webp

427 ms

TN_LP_MOBILE_160724.jpg

TN_LP_MOBILE_160724.jpg

418 ms

TN_PK_MOBILE_160724.jpg

TN_PK_MOBILE_160724.jpg

417 ms

TN_HP_2X1_MOBILE160724.jpg

TN_HP_2X1_MOBILE160724.jpg

419 ms

LEGENDS_logo_white.svg

LEGENDS_logo_white.svg

416 ms

amex.svg

amex.svg

421 ms

visa.svg

visa.svg

421 ms

mastercard.svg

mastercard.svg

419 ms

discover.svg

discover.svg

423 ms

bitcoins.svg

bitcoins.svg

422 ms

text.min.js

text.min.js

413 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0C4n.ttf

92 ms

opensans-400.woff

opensans-400.woff

91 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjr0C4n.ttf

377 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0C4n.ttf

377 ms

opensans-300.woff

opensans-300.woff

89 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1y4n.ttf

384 ms

opensans-600.woff

opensans-600.woff

343 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1y4n.ttf

379 ms

opensans-700.woff

opensans-700.woff

89 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1y4n.ttf

381 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkyFjaVc.ttf

382 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk0ZjaVc.ttf

381 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0RkxhjaVc.ttf

381 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk_RkaVc.ttf

387 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk8ZkaVc.ttf

386 ms

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVc.ttf

memQYaGs126MiZpBA-UFUIcVXSCEkx2cmqvXlWq8tWZ0Pw86hd0Rk5hkaVc.ttf

386 ms

porto-icons.woff

porto-icons.woff

86 ms

fa-regular-400.woff

fa-regular-400.woff

85 ms

fa-solid-900.woff

fa-solid-900.woff

340 ms

fa-brands-400.woff

fa-brands-400.woff

341 ms

js-translation.json

js-translation.json

296 ms

moment.min.js

moment.min.js

288 ms

Accessibility Review

sweetpee.com accessibility score

85

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 are not valid or misspelled

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

sweetpee.com 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

Missing source maps for large first-party JavaScript

SEO Factors

sweetpee.com SEO score

89

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

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

sweetpee.com

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