Tools & Wizards About Us
nastyncig.com screenshot

Report Summary

  • 61

    Performance

    Renders faster than
    76% 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

nastyncig.com

Nasty NCIG | NASTY NCIG Online Store | FREE SHIPPING

Page Load Speed

8.5 sec in total

First Response

495 ms

Resources Loaded

6.1 sec

Page Rendered

1.9 sec

nastyncig.com screenshot

About Website

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

Get your NASTY products such as NASTY FIX POD, NASTY FIX GO 3000 & 5000 from our NASTY NCIG Online Store. WORLDWIDE SHIPPING.

Visit nastyncig.com

Key Findings

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

Performance Metrics

nastyncig.com performance score

61

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

11/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

26/100

25%

SI (Speed Index)

Value7.3 s

29/100

10%

TBT (Total Blocking Time)

Value100 ms

98/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value6.0 s

64/100

10%

Network Requests Diagram

nastyncig.com

495 ms

nastyncig.com

1182 ms

font-awesome.min.css

234 ms

style-index.css

465 ms

mediaelementplayer-legacy.min.css

696 ms

Our browser made a total of 112 requests to load all elements on the main page. We found that 73% of them (82 requests) were addressed to the original Nastyncig.com, 16% (18 requests) were made to Fonts.gstatic.com and 5% (6 requests) were made to Lh3.googleusercontent.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Nastyncig.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 289.1 kB (45%)

Content Size

636.9 kB

After Optimization

347.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nastyncig.com main page is 636.9 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. 60% of websites need less resources to load. HTML takes 326.9 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 285.3 kB

  • Original 326.9 kB
  • After minification 323.2 kB
  • After compression 41.7 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 285.3 kB or 87% of the original size.

Image Optimization

-2%

Potential reduce by 2.7 kB

  • Original 115.6 kB
  • After minification 112.9 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. Nasty NCIG images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 120 B

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

CSS Optimization

-1%

Potential reduce by 1.1 kB

  • Original 182.2 kB
  • After minification 182.2 kB
  • After compression 181.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. Nastyncig.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 46 (51%)

Requests Now

91

After Optimization

45

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nastyncig.com

nastyncig.com

495 ms

nastyncig.com

nastyncig.com

1182 ms

font-awesome.min.css

font-awesome.min.css

234 ms

style-index.css

style-index.css

465 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

696 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

705 ms

dispensary-age-verification-public.min.css

dispensary-age-verification-public.min.css

729 ms

font-icons.css

font-icons.css

987 ms

frontend.css

frontend.css

735 ms

woocommerce-layout.css

woocommerce-layout.css

744 ms

woocommerce.css

woocommerce.css

927 ms

hint.min.css

hint.min.css

937 ms

perfect-scrollbar.min.css

perfect-scrollbar.min.css

972 ms

custom-theme.css

custom-theme.css

980 ms

fonts.css

fonts.css

994 ms

frontend.css

frontend.css

1160 ms

frontend.css

frontend.css

1171 ms

woo-conditional-payments.css

woo-conditional-payments.css

1214 ms

woo-conditional-shipping.css

woo-conditional-shipping.css

1224 ms

style.min.css

style.min.css

1231 ms

theme.min.css

theme.min.css

1238 ms

frontend.min.css

frontend.min.css

1390 ms

frontend.min.css

frontend.min.css

1641 ms

swiper.min.css

swiper.min.css

1457 ms

post-24.css

post-24.css

1467 ms

frontend.min.css

frontend.min.css

1731 ms

she-header-style.css

she-header-style.css

1493 ms

global.css

global.css

1620 ms

post-8172.css

post-8172.css

1701 ms

post-356105.css

post-356105.css

1711 ms

post-356118.css

post-356118.css

1742 ms

free-shipping.css

free-shipping.css

1851 ms

style.css

style.css

1874 ms

footable.core.css

footable.core.css

1943 ms

bootstrap.css

bootstrap.css

1955 ms

select2.css

select2.css

1976 ms

checkout-blocks.css

checkout-blocks.css

1984 ms

css

css

38 ms

s-202410.js

s-202410.js

21 ms

e-202410.js

e-202410.js

21 ms

featherlight.css

featherlight.css

2078 ms

frontend.css

frontend.css

1881 ms

frontend.css

frontend.css

1729 ms

woocommerce.css

woocommerce.css

1509 ms

jetpack.css

jetpack.css

1527 ms

trustindex-google-widget.css

trustindex-google-widget.css

1603 ms

wpforms-full.min.css

wpforms-full.min.css

1599 ms

lazyload.min.js

lazyload.min.js

1651 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff

122 ms

font

font

147 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aXw.woff

146 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aXw.woff

146 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aXw.woff

145 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aXw.woff

145 ms

font

font

145 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aXw.woff

188 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aXw.woff

187 ms

woofc.ttf

woofc.ttf

253 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT6jRZ9xdv.woff

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT6jRZ9xdv.woff

186 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT0zRZ9xdv.woff

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTT0zRZ9xdv.woff

187 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDRZ9xdv.woff

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDRZ9xdv.woff

187 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTnTRZ9xdv.woff

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTnTRZ9xdv.woff

187 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTBjNZ9xdv.woff

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTBjNZ9xdv.woff

229 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDNZ9xdv.woff

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDNZ9xdv.woff

229 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTajNZ9xdv.woff

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTajNZ9xdv.woff

229 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDNZ9xdv.woff

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTtDNZ9xdv.woff

230 ms

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDJZ9xdv.woff

k3k6o8UDI-1M0wlSV9XAw6lQkqWY8Q82sJaRE-NWIDdgffTTNDJZ9xdv.woff

229 ms

logo.svg

logo.svg

148 ms

AD5-WCkwwBlJL5gZyBMBKy--0HY1-NT5f7WjMtHb56JW=s120-c-c-rp-w64-h64-mo-br100

AD5-WCkwwBlJL5gZyBMBKy--0HY1-NT5f7WjMtHb56JW=s120-c-c-rp-w64-h64-mo-br100

410 ms

NASTY-NCIG-Header-Logo.webp

NASTY-NCIG-Header-Logo.webp

255 ms

NCIG-NCIG-Pro-Devices-and-Flavours-Banner.webp

NCIG-NCIG-Pro-Devices-and-Flavours-Banner.webp

738 ms

NCIG-NASTY-Bar-DR12KI-Banner.webp

NCIG-NASTY-Bar-DR12KI-Banner.webp

741 ms

Ncig-Loyalty-Point-01.webp

Ncig-Loyalty-Point-01.webp

476 ms

Badges-01-150x150.webp

Badges-01-150x150.webp

256 ms

Badges-02-150x150.webp

Badges-02-150x150.webp

353 ms

Badges-03-150x150.webp

Badges-03-150x150.webp

500 ms

Badges-04-150x150.webp

Badges-04-150x150.webp

504 ms

Nasty-Bar-Trio-Starter-Pack-300x300.jpg

Nasty-Bar-Trio-Starter-Pack-300x300.jpg

585 ms

Nasty-Bar-Double-Up-Bundle-300x300.jpg

Nasty-Bar-Double-Up-Bundle-300x300.jpg

710 ms

Nasty-Bar-Triple-Threat-Combo-300x300.jpg

Nasty-Bar-Triple-Threat-Combo-300x300.jpg

746 ms

Nasty-Bar-Quadruple-Bliss-300x300.jpg

Nasty-Bar-Quadruple-Bliss-300x300.jpg

750 ms

NCIG-Pro-Combo-DuoMix-300x300.webp

NCIG-Pro-Combo-DuoMix-300x300.webp

816 ms

NCIG-Pro-Combo-TrioBlend-300x300.webp

NCIG-Pro-Combo-TrioBlend-300x300.webp

944 ms

Combo-NCIG-Pro-Device-v1-03-300x300.webp

Combo-NCIG-Pro-Device-v1-03-300x300.webp

980 ms

Combo-NCIG-Pro-Device-v1-04-300x300.webp

Combo-NCIG-Pro-Device-v1-04-300x300.webp

983 ms

NCIG-Pod-Duo-300x300.webp

NCIG-Pod-Duo-300x300.webp

991 ms

NCIG-Pod-Trio-300x300.webp

NCIG-Pod-Trio-300x300.webp

996 ms

Combo-NCIG-Pod-Pro-v1-03-300x300.webp

Combo-NCIG-Pod-Pro-v1-03-300x300.webp

1046 ms

Combo-NCIG-Pod-Pro-v1-04-300x300.webp

Combo-NCIG-Pod-Pro-v1-04-300x300.webp

1178 ms

NCIG-PRO-DEVICE-MIDNIGHT-300x300.webp

NCIG-PRO-DEVICE-MIDNIGHT-300x300.webp

1222 ms

NCIG-PRO-Unbeatable-300x300.webp

NCIG-PRO-Unbeatable-300x300.webp

1227 ms

NCIG-PRO-DEVICE-Tiffany-300x300.webp

NCIG-PRO-DEVICE-Tiffany-300x300.webp

1237 ms

NCIG-PRO-DEVICE-Sangria-300x300.webp

NCIG-PRO-DEVICE-Sangria-300x300.webp

1242 ms

NCIG-POD-Double-Grape-300x300.webp

NCIG-POD-Double-Grape-300x300.webp

1277 ms

NCIG-POD-Coffee-Caramel-300x300.webp

NCIG-POD-Coffee-Caramel-300x300.webp

1412 ms

NCIG-POD-Banana-Vanilla-300x300.webp

NCIG-POD-Banana-Vanilla-300x300.webp

1465 ms

NCIG-POD-Buttery-Toffe-300x300.webp

NCIG-POD-Buttery-Toffe-300x300.webp

1471 ms

NCIG-POD-Blanc-Classic-300x300.webp

NCIG-POD-Blanc-Classic-300x300.webp

1483 ms

NCIG-POD-Blanc-Premium-300x300.webp

NCIG-POD-Blanc-Premium-300x300.webp

1488 ms

NCIG-POD-Coffe-300x300.webp

NCIG-POD-Coffe-300x300.webp

1507 ms

NCIG-POD-Guava-300x300.webp

NCIG-POD-Guava-300x300.webp

1645 ms

FINEST-OUNCE-Google-Maps-150x150.png

FINEST-OUNCE-Google-Maps-150x150.png

1707 ms

FINEST-OUNCE-Waze-150x150.png

FINEST-OUNCE-Waze-150x150.png

1714 ms

FINEST-OUNCE-WhatsApp.png

FINEST-OUNCE-WhatsApp.png

1728 ms

AD5-WCk6k7wCyUSCv3xqReKfQYUeai3xjuAjEAV-KpT5RQ=s120-c-c-rp-w64-h64-mo-ba4-br100

AD5-WCk6k7wCyUSCv3xqReKfQYUeai3xjuAjEAV-KpT5RQ=s120-c-c-rp-w64-h64-mo-ba4-br100

582 ms

AD5-WCmBG88iJ307Chugv7v6zlu_GVnBqY1MyazrjnY4=s120-c-c-rp-w64-h64-mo-ba3-br100

AD5-WCmBG88iJ307Chugv7v6zlu_GVnBqY1MyazrjnY4=s120-c-c-rp-w64-h64-mo-ba3-br100

466 ms

AEdFTp6mcFQS-piEVxLXIsR_nPP_OQsbGkmxa3hrnzkU=s120-c-c-rp-w64-h64-mo-br100

AEdFTp6mcFQS-piEVxLXIsR_nPP_OQsbGkmxa3hrnzkU=s120-c-c-rp-w64-h64-mo-br100

539 ms

AD5-WCknV9FEXxhGeDHfBHnccL4Adf0ESOJCw7EdCgDPqA=s120-c-c-rp-w64-h64-mo-br100

AD5-WCknV9FEXxhGeDHfBHnccL4Adf0ESOJCw7EdCgDPqA=s120-c-c-rp-w64-h64-mo-br100

720 ms

AD5-WCn0MbDjkaDmMe9-BOiAooWxsuCK0fbjp6zQOCJHk28=s120-c-c-rp-w64-h64-mo-ba2-br100

AD5-WCn0MbDjkaDmMe9-BOiAooWxsuCK0fbjp6zQOCJHk28=s120-c-c-rp-w64-h64-mo-ba2-br100

627 ms

embed

embed

214 ms

js

js

56 ms

woocommerce-smallscreen.css

woocommerce-smallscreen.css

232 ms

Accessibility Review

nastyncig.com 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-hidden="true"] elements contain focusable descendents

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.

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

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

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

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

SEO Factors

nastyncig.com 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 Nastyncig.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 Nastyncig.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

nastyncig.com

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