Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

geniestage.wpengine.com

Decarboxylation Made Easy - Activate THC and CBD | Ardent Cannabis

Page Load Speed

3.8 sec in total

First Response

190 ms

Resources Loaded

2.6 sec

Page Rendered

1 sec

geniestage.wpengine.com screenshot

About Website

Welcome to geniestage.wpengine.com homepage info - get ready to check Geniestage Wpengine best content for United States right away, or after learning these important things about geniestage.wpengine.com

Ardent FX & Nova Decarboxylators are a discreet smell-free solution to decarb, infusion & edibles. Save money & accurately dose cannabis.

Visit geniestage.wpengine.com

Key Findings

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

Performance Metrics

geniestage.wpengine.com performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.5 s

6/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value11.2 s

5/100

10%

TBT (Total Blocking Time)

Value2,520 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value0.184

66/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

geniestage.wpengine.com

190 ms

autoptimize_f752770954c6cea9f7ab908a3fe34ffe.css

92 ms

autoptimize_18b1eed8f66b313ecbf9f5a822f04192.css

124 ms

js

85 ms

jquery.min.js

129 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that 15% of them (8 requests) were addressed to the original Geniestage.wpengine.com, 15% (8 requests) were made to Static.klaviyo.com and 11% (6 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (405 ms) relates to the external source Collector.leaddyno.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 213.4 kB (34%)

Content Size

634.8 kB

After Optimization

421.4 kB

In fact, the total size of Geniestage.wpengine.com main page is 634.8 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. 55% of websites need less resources to load. Javascripts take 275.3 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 198.0 kB

  • Original 238.0 kB
  • After minification 237.9 kB
  • After compression 40.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. 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 198.0 kB or 83% of the original size.

JavaScript Optimization

-1%

Potential reduce by 3.4 kB

  • Original 275.3 kB
  • After minification 275.3 kB
  • After compression 271.9 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

-10%

Potential reduce by 12.0 kB

  • Original 121.5 kB
  • After minification 121.5 kB
  • After compression 109.5 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. Geniestage.wpengine.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 36 (71%)

Requests Now

51

After Optimization

15

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

Accessibility Review

geniestage.wpengine.com accessibility score

74

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 input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

geniestage.wpengine.com best practices score

83

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

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

geniestage.wpengine.com SEO score

79

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

High

Page is blocked from indexing

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 Geniestage.wpengine.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 Geniestage.wpengine.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

Open Graph data is detected on the main page of PARSED_DOMAIN, but there is no image specified in description. It would be a good idea for the website admin to select a nice image that can properly represent the website in Open Graph data, otherwise the first found image will be taken for this purpose and social media information block will look like this: