Tools & Wizards About Us
notsosmelly.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

notsosmelly.com

澳门金碧汇彩娱乐场-金碧汇彩网址-金碧汇彩娱乐网址

Page Load Speed

6.4 sec in total

First Response

339 ms

Resources Loaded

4.7 sec

Page Rendered

1.4 sec

notsosmelly.com screenshot

About Website

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

_ _ _澳门金碧汇彩娱乐场指数网作为专业即时数据平台，为大家提供最快速、最准确、最全面的专业级交易数据.金碧汇彩网址亚洲最著名的游戏平台之一.金碧汇彩娱乐网址是英国在线体育娱乐平台，创立于2000年，并曾获得英女王颁发杰出商业成就奖!

Visit notsosmelly.com

Key Findings

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

notsosmelly.com performance score

0

Network Requests Diagram

www.notsosmelly.com

339 ms

jquery-ui.css

142 ms

timber.scss.css

246 ms

theme.scss.css

1952 ms

css

149 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Notsosmelly.com, 75% (39 requests) were made to Cdn.shopify.com and 4% (2 requests) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (2 sec) relates to the external source Cdn.shopify.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 698.2 kB (29%)

Content Size

2.4 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Notsosmelly.com main page is 2.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. 50% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 50.4 kB

  • Original 58.0 kB
  • After minification 41.7 kB
  • After compression 7.6 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 16.2 kB, which is 28% 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 50.4 kB or 87% of the original size.

Image Optimization

-5%

Potential reduce by 82.8 kB

  • Original 1.6 MB
  • After minification 1.5 MB

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. Notsosmelly images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 279.1 kB

  • Original 406.7 kB
  • After minification 391.5 kB
  • After compression 127.6 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 279.1 kB or 69% of the original size.

CSS Optimization

-81%

Potential reduce by 285.9 kB

  • Original 352.5 kB
  • After minification 351.8 kB
  • After compression 66.6 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. Notsosmelly.com needs all CSS files to be minified and compressed as it can save up to 285.9 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (35%)

Requests Now

49

After Optimization

32

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.notsosmelly.com

www.notsosmelly.com

339 ms

jquery-ui.css

jquery-ui.css

142 ms

timber.scss.css

timber.scss.css

246 ms

theme.scss.css

theme.scss.css

1952 ms

css

css

149 ms

jquery.min.js

jquery.min.js

194 ms

modernizr.min.js

modernizr.min.js

512 ms

jquery-ui.js

jquery-ui.js

688 ms

fastclick.min.js

fastclick.min.js

584 ms

timber.js

timber.js

983 ms

theme.js

theme.js

203 ms

slick.min.js

slick.min.js

304 ms

slick-theme.js

slick-theme.js

298 ms

magnific-popup.min.js

magnific-popup.min.js

854 ms

shopify_stats.js

shopify_stats.js

119 ms

trekkie.storefront.min.js

trekkie.storefront.min.js

638 ms

logo.png

logo.png

464 ms

hero_slide_1.jpg

hero_slide_1.jpg

796 ms

hero_slide_2.jpg

hero_slide_2.jpg

643 ms

hero_slide_3.jpg

hero_slide_3.jpg

643 ms

aqua-rda-atomizer_large.jpeg

aqua-rda-atomizer_large.jpeg

226 ms

7430e072-660f-464d-b1ea-ae9839db3736_large.jpg

7430e072-660f-464d-b1ea-ae9839db3736_large.jpg

455 ms

cbd-label-creamberry_large.jpeg

cbd-label-creamberry_large.jpeg

573 ms

26650-mac-150-watt-mod1_large.jpeg

26650-mac-150-watt-mod1_large.jpeg

1982 ms

devine_0d2dc62e-afae-40d2-91f2-14bfcb9a9875_large.jpg

devine_0d2dc62e-afae-40d2-91f2-14bfcb9a9875_large.jpg

692 ms

caravela1_large.jpeg

caravela1_large.jpeg

649 ms

HCM001-8_large.jpg

HCM001-8_large.jpg

692 ms

cbd-label-Fudge-Brownies_large.jpeg

cbd-label-Fudge-Brownies_large.jpeg

725 ms

cbd-label-Raspberry-Cheesecake_large.jpeg

cbd-label-Raspberry-Cheesecake_large.jpeg

902 ms

Cerebrus-RDA_large.png

Cerebrus-RDA_large.png

1263 ms

chi-you-2_large.jpeg

chi-you-2_large.jpeg

783 ms

cut2_large.jpg

cut2_large.jpg

879 ms

Dreadnaught-Mod_large.jpeg

Dreadnaught-Mod_large.jpeg

1173 ms

Wood-box-7_large.jpeg

Wood-box-7_large.jpeg

976 ms

EGO-Starter-Kit-Box-Set-Pic_large.jpeg

EGO-Starter-Kit-Box-Set-Pic_large.jpeg

974 ms

ipv-mini-30watt_large.jpeg

ipv-mini-30watt_large.jpeg

1040 ms

kayfun_lite_clone_large.jpeg

kayfun_lite_clone_large.jpeg

1067 ms

krypto_large.jpeg

krypto_large.jpeg

1040 ms

evapelargebottle_edb5f8e6-e49d-4d3e-a2cf-23f75e25a5e2_large.jpg

evapelargebottle_edb5f8e6-e49d-4d3e-a2cf-23f75e25a5e2_large.jpg

1185 ms

magma-rda_large.jpeg

magma-rda_large.jpeg

1258 ms

Maraxus3_large.jpeg

Maraxus3_large.jpeg

1186 ms

icons.woff

icons.woff

1164 ms

icons.woff

icons.woff

1235 ms

ajax-loader.gif

ajax-loader.gif

1120 ms

K3JwgRfHfP8

K3JwgRfHfP8

578 ms

record.gif

record.gif

182 ms

identify

identify

333 ms

page

page

320 ms

www-embed-player-vfl-z2BtK.css

www-embed-player-vfl-z2BtK.css

323 ms

www-embed-player.js

www-embed-player.js

427 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

245 ms

ad_status.js

ad_status.js

244 ms

SEO Factors

notsosmelly.com SEO score

0

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Notsosmelly.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it does not match the claimed English language. Our system also found out that Notsosmelly.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

notsosmelly.com

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