Tools & Wizards About Us
bluntandenvy.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

bluntandenvy.com

Official Blunt & Envy Scooters |Scooters & Parts

Page Load Speed

6 sec in total

First Response

1.5 sec

Resources Loaded

4.2 sec

Page Rendered

310 ms

bluntandenvy.com screenshot

About Website

Welcome to bluntandenvy.com homepage info - get ready to check Blunt And Envy best content for United States right away, or after learning these important things about bluntandenvy.com

Home of Blunt & Envy Scooters, known for innovative high quality parts at an affordable price.

Visit bluntandenvy.com

Key Findings

We analyzed Bluntandenvy.com page load time and found that the first response time was 1.5 sec and then it took 4.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

bluntandenvy.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value13.9 s

0/100

25%

SI (Speed Index)

Value12.6 s

3/100

10%

TBT (Total Blocking Time)

Value10,740 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.185

66/100

15%

TTI (Time to Interactive)

Value32.0 s

0/100

10%

Network Requests Diagram

www.bluntandenvy.com

1471 ms

wp-emoji-release.min.js

73 ms

toolbar.css

148 ms

style.css

139 ms

jquery-ui.theme.min.css

152 ms

Our browser made a total of 107 requests to load all elements on the main page. We found that 53% of them (57 requests) were addressed to the original Bluntandenvy.com, 9% (10 requests) were made to Static.xx.fbcdn.net and 7% (8 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Bluntandenvy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 452.1 kB (31%)

Content Size

1.4 MB

After Optimization

987.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bluntandenvy.com main page is 1.4 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. 70% of websites need less resources to load. Images take 753.3 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 47.8 kB

  • Original 61.0 kB
  • After minification 58.3 kB
  • After compression 13.1 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 47.8 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 22.5 kB

  • Original 753.3 kB
  • After minification 730.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. Blunt And Envy images are well optimized though.

JavaScript Optimization

-51%

Potential reduce by 230.3 kB

  • Original 451.3 kB
  • After minification 422.8 kB
  • After compression 221.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 230.3 kB or 51% of the original size.

CSS Optimization

-87%

Potential reduce by 151.4 kB

  • Original 174.4 kB
  • After minification 145.4 kB
  • After compression 22.9 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. Bluntandenvy.com needs all CSS files to be minified and compressed as it can save up to 151.4 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 60 (61%)

Requests Now

98

After Optimization

38

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.bluntandenvy.com

www.bluntandenvy.com

1471 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

73 ms

toolbar.css

toolbar.css

148 ms

style.css

style.css

139 ms

jquery-ui.theme.min.css

jquery-ui.theme.min.css

152 ms

minimalist.css

minimalist.css

15 ms

gsc.css

gsc.css

136 ms

styles.css

styles.css

150 ms

pagenavi-css.css

pagenavi-css.css

147 ms

tabulous.css

tabulous.css

205 ms

sc-styles.css

sc-styles.css

205 ms

jquery.js

jquery.js

336 ms

jquery-migrate.min.js

jquery-migrate.min.js

208 ms

flags.js

flags.js

210 ms

toolbar.js

toolbar.js

208 ms

load-toolbar.js

load-toolbar.js

272 ms

wp-sc-ajax.js

wp-sc-ajax.js

273 ms

gsc.js

gsc.js

274 ms

jsapi

jsapi

31 ms

jquery.lazyload.min.js

jquery.lazyload.min.js

276 ms

tabulous.js

tabulous.js

277 ms

script-tab.js

script-tab.js

358 ms

jquery.elevatezoom.js

jquery.elevatezoom.js

359 ms

script-gallery-product.js

script-gallery-product.js

358 ms

style.css

style.css

361 ms

all.js

all.js

270 ms

element.js

element.js

34 ms

core.min.js

core.min.js

359 ms

widget.min.js

widget.min.js

401 ms

mouse.min.js

mouse.min.js

415 ms

resizable.min.js

resizable.min.js

407 ms

draggable.min.js

draggable.min.js

415 ms

button.min.js

button.min.js

414 ms

position.min.js

position.min.js

412 ms

dialog.min.js

dialog.min.js

468 ms

jquery.form.min.js

jquery.form.min.js

475 ms

scripts.js

scripts.js

481 ms

wp-embed.min.js

wp-embed.min.js

496 ms

minimalist.css

minimalist.css

30 ms

reset.css

reset.css

125 ms

css

css

24 ms

css

css

37 ms

14 ms

bg-footer-semitransparent.png

bg-footer-semitransparent.png

92 ms

logo-image-white.png

logo-image-white.png

89 ms

1-320x175.jpg

1-320x175.jpg

136 ms

derek-2-320x175.jpg

derek-2-320x175.jpg

90 ms

19-320x175.jpg

19-320x175.jpg

134 ms

1-250x180.jpg

1-250x180.jpg

134 ms

derek-2-250x180.jpg

derek-2-250x180.jpg

137 ms

19-250x180.jpg

19-250x180.jpg

140 ms

scooter-stripper-black-featured-145x215.jpg

scooter-stripper-black-featured-145x215.jpg

150 ms

integrated-headset-red-featured-145x215.jpg

integrated-headset-red-featured-145x215.jpg

308 ms

default+en.css

default+en.css

4 ms

default+en.I.js

default+en.I.js

10 ms

facebook-off.png

facebook-off.png

266 ms

instagram-off.png

instagram-off.png

262 ms

youtube-off.png

youtube-off.png

266 ms

btn_back.png

btn_back.png

829 ms

btn_pause.png

btn_pause.png

885 ms

btn_next.png

btn_next.png

903 ms

bg-title.png

bg-title.png

258 ms

bg-title-sidebar.png

bg-title-sidebar.png

258 ms

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

cJZKeOuBrn4kERxqtaUH3SZ2oysoEQEeKwjgmXLRnTc.ttf

33 ms

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

k3k702ZOKiLJc3WVjuplzJS3E-kSBmtLoNJPDtbj2Pk.ttf

34 ms

gk5FxslNkTTHtojXrkp-xEb5azEPpng8GbF4Y4e4kqzr7w4p9aSvGirXi6XmeXNA.ttf

gk5FxslNkTTHtojXrkp-xEb5azEPpng8GbF4Y4e4kqzr7w4p9aSvGirXi6XmeXNA.ttf

11 ms

gk5FxslNkTTHtojXrkp-xGtXp_56cyzG87rk01y3A5nr7w4p9aSvGirXi6XmeXNA.ttf

gk5FxslNkTTHtojXrkp-xGtXp_56cyzG87rk01y3A5nr7w4p9aSvGirXi6XmeXNA.ttf

11 ms

45 ms

xd_arbiter.php

xd_arbiter.php

244 ms

xd_arbiter.php

xd_arbiter.php

451 ms

translateelement.css

translateelement.css

64 ms

main.js

main.js

86 ms

element_main.js

element_main.js

113 ms

sdk.js

sdk.js

150 ms

bg-footer.png

bg-footer.png

233 ms

flags.png

flags.png

193 ms

ui-bg_flat_75_ffffff_40x100.png

ui-bg_flat_75_ffffff_40x100.png

98 ms

ui-icons_222222_256x240.png

ui-icons_222222_256x240.png

123 ms

bg-4.jpg

bg-4.jpg

280 ms

Jesse-deck.png

Jesse-deck.png

520 ms

translate_24dp.png

translate_24dp.png

37 ms

l

l

48 ms

googlelogo_color_42x16dp.png

googlelogo_color_42x16dp.png

33 ms

like_box.php

like_box.php

77 ms

ebiMDO3r-8l.css

ebiMDO3r-8l.css

285 ms

jGc-59L_9lo.css

jGc-59L_9lo.css

353 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

489 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

620 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

512 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

510 ms

12524083_1190347967645410_3623453536785386560_n.jpg

12524083_1190347967645410_3623453536785386560_n.jpg

287 ms

11988452_1114292935250914_7283336252187645824_n.jpg

11988452_1114292935250914_7283336252187645824_n.jpg

355 ms

10407738_794094393992719_558448208420832897_n.jpg

10407738_794094393992719_558448208420832897_n.jpg

424 ms

12742028_895986767176146_7318741226256019403_n.jpg

12742028_895986767176146_7318741226256019403_n.jpg

488 ms

149812_426451334088562_950051514_n.jpg

149812_426451334088562_950051514_n.jpg

492 ms

12105985_836966363087197_2040157106613150162_n.jpg

12105985_836966363087197_2040157106613150162_n.jpg

492 ms

10985324_769531899792580_4512184938995005801_n.jpg

10985324_769531899792580_4512184938995005801_n.jpg

492 ms

1970735_462851910588623_9127530875956628062_n.jpg

1970735_462851910588623_9127530875956628062_n.jpg

493 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

75 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

76 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

74 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

76 ms

async-ads.js

async-ads.js

47 ms

google_custom_search_watermark.gif

google_custom_search_watermark.gif

41 ms

button-search.png

button-search.png

71 ms

small-logo.png

small-logo.png

25 ms

clear.gif

clear.gif

26 ms

Accessibility Review

bluntandenvy.com accessibility score

81

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

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

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

bluntandenvy.com SEO score

92

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

bluntandenvy.com

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