Tools & Wizards About Us
ihempx.com screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 99

    SEO

    Google-friendlier than
    93% of websites

ihempx.com

iHEMPx | Order Hemp Seeds & Hemp Starts | High CBD & CBG

Page Load Speed

2.4 sec in total

First Response

73 ms

Resources Loaded

1.9 sec

Page Rendered

466 ms

ihempx.com screenshot

About Website

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

iHEMPx is your one-stop-shop for feminized hemp seeds, hemp starts, CBD, CBG, industrial hemp and certified compliant hemp varietals.

Visit ihempx.com

Key Findings

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

ihempx.com performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value13.0 s

0/100

25%

SI (Speed Index)

Value5.1 s

62/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value9.9 s

27/100

10%

Network Requests Diagram

ihempx.com

73 ms

ihempx.com

113 ms

wpp.min.js

13 ms

2841m.css

43 ms

2iqp9.css

34 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 74% of them (51 requests) were addressed to the original Ihempx.com, 13% (9 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Ihempx.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 309.0 kB (16%)

Content Size

2.0 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ihempx.com main page is 2.0 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 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 117.6 kB

  • Original 146.4 kB
  • After minification 139.7 kB
  • After compression 28.9 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 117.6 kB or 80% of the original size.

Image Optimization

-0%

Potential reduce by 723 B

  • Original 1.3 MB
  • After minification 1.3 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. IHEMPx images are well optimized though.

JavaScript Optimization

-33%

Potential reduce by 74.9 kB

  • Original 225.2 kB
  • After minification 223.8 kB
  • After compression 150.3 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 74.9 kB or 33% of the original size.

CSS Optimization

-48%

Potential reduce by 115.9 kB

  • Original 243.0 kB
  • After minification 243.0 kB
  • After compression 127.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. Ihempx.com needs all CSS files to be minified and compressed as it can save up to 115.9 kB or 48% of the original size.

Requests Breakdown

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

Requests Now

57

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ihempx.com

ihempx.com

73 ms

ihempx.com

ihempx.com

113 ms

wpp.min.js

wpp.min.js

13 ms

2841m.css

2841m.css

43 ms

2iqp9.css

2iqp9.css

34 ms

2iqp9.css

2iqp9.css

21 ms

2iqrx.css

2iqrx.css

30 ms

2iqp9.css

2iqp9.css

22 ms

post-100004148.css

post-100004148.css

29 ms

2iqp9.css

2iqp9.css

47 ms

post-100004500.css

post-100004500.css

46 ms

css

css

59 ms

2iqp9.css

2iqp9.css

49 ms

css

css

78 ms

2iqp9.js

2iqp9.js

53 ms

2iqp9.js

2iqp9.js

48 ms

js

js

95 ms

3twl3.js

3twl3.js

50 ms

4bfgp.js

4bfgp.js

51 ms

3twl3.js

3twl3.js

51 ms

3twl3.js

3twl3.js

53 ms

6immx.css

6immx.css

52 ms

lazysizes.min.js

lazysizes.min.js

53 ms

track.js

track.js

57 ms

frontend.min.js

frontend.min.js

57 ms

scripts.js

scripts.js

57 ms

element.js

element.js

71 ms

woocommerce.min.js

woocommerce.min.js

59 ms

site_main.js

site_main.js

59 ms

awdr-dynamic-price.js

awdr-dynamic-price.js

63 ms

frontend.js

frontend.js

64 ms

script.js

script.js

64 ms

cart-fragments.min.js

cart-fragments.min.js

64 ms

script.js

script.js

65 ms

sourcebuster.min.js

sourcebuster.min.js

62 ms

order-attribution.min.js

order-attribution.min.js

69 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

69 ms

webpack.runtime.min.js

webpack.runtime.min.js

67 ms

frontend-modules.min.js

frontend-modules.min.js

87 ms

hooks.min.js

hooks.min.js

71 ms

i18n.min.js

i18n.min.js

70 ms

frontend.min.js

frontend.min.js

86 ms

waypoints.min.js

waypoints.min.js

80 ms

core.min.js

core.min.js

67 ms

frontend.min.js

frontend.min.js

67 ms

elements-handlers.min.js

elements-handlers.min.js

62 ms

widget

widget

370 ms

iHEMPx_Website_logo.png

iHEMPx_Website_logo.png

73 ms

20191001_134040-scaled.jpg

20191001_134040-scaled.jpg

75 ms

Seeds.jpg

Seeds.jpg

72 ms

iHEMPx-Equip.jpg

iHEMPx-Equip.jpg

73 ms

processed-hemp-1000-2.jpg

processed-hemp-1000-2.jpg

74 ms

Contracthempfarming.jpg

Contracthempfarming.jpg

73 ms

flags.png

flags.png

13 ms

ihempx.com

ihempx.com

1415 ms

7cHpv4kjgoGqM7E_DMs8.ttf

7cHpv4kjgoGqM7E_DMs8.ttf

19 ms

7cHqv4kjgoGqM7E3_-gs51op.ttf

7cHqv4kjgoGqM7E3_-gs51op.ttf

35 ms

7cHqv4kjgoGqM7E3p-ks51op.ttf

7cHqv4kjgoGqM7E3p-ks51op.ttf

46 ms

7cHqv4kjgoGqM7E3w-os51op.ttf

7cHqv4kjgoGqM7E3w-os51op.ttf

46 ms

7cHrv4kjgoGqM7E3b_s7wHo.ttf

7cHrv4kjgoGqM7E3b_s7wHo.ttf

47 ms

7cHqv4kjgoGqM7E30-8s51op.ttf

7cHqv4kjgoGqM7E30-8s51op.ttf

47 ms

7cHqv4kjgoGqM7E3t-4s51op.ttf

7cHqv4kjgoGqM7E3t-4s51op.ttf

46 ms

7cHqv4kjgoGqM7E3q-0s51op.ttf

7cHqv4kjgoGqM7E3q-0s51op.ttf

46 ms

7cHqv4kjgoGqM7E3j-ws51op.ttf

7cHqv4kjgoGqM7E3j-ws51op.ttf

47 ms

website

website

330 ms

floatbutton1_0uA5KIDjSJBNGPeiRDI3YtNcjWJ9mZsPq48NM5iMzp7_jWYVkIHbMtgrDX_xil60_.css

floatbutton1_0uA5KIDjSJBNGPeiRDI3YtNcjWJ9mZsPq48NM5iMzp7_jWYVkIHbMtgrDX_xil60_.css

100 ms

floatbutton1_Thjot1_ijmUDxJNcgVhQgbjvVoqkC76taLNxs5xr2mctXg9qs3uyEWffHAD9jHqf_.js

floatbutton1_Thjot1_ijmUDxJNcgVhQgbjvVoqkC76taLNxs5xr2mctXg9qs3uyEWffHAD9jHqf_.js

136 ms

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

siq_mpWsf52LIPg9mU40fjRdjF6WMUs-Q0VNu4KH07GkhNZGQTRxW2eRyFJLAq9VKCYB_.ttf

22 ms

2iqp9.css

2iqp9.css

6 ms

Accessibility Review

ihempx.com accessibility score

95

Accessibility Issues

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

Links do not have a discernible name

Best Practices

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

ihempx.com SEO score

99

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

ihempx.com

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