Tools & Wizards About Us
ashitabaplant.com screenshot

Report Summary

  • 39

    Performance

    Renders faster than
    58% of other websites

  • 55

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

ashitabaplant.com

Ashitaba Plant - This incredible green has tons of health benefits.

Page Load Speed

22.1 sec in total

First Response

220 ms

Resources Loaded

21.4 sec

Page Rendered

448 ms

ashitabaplant.com screenshot

About Website

Welcome to ashitabaplant.com homepage info - get ready to check Ashitaba Plant best content for Philippines right away, or after learning these important things about ashitabaplant.com

A blog about the benefits of ashitaba, tomorrow leaves, how to make ashitaba tea, how to grow and harvest ashitaba and the wonders of ashitaba.

Visit ashitabaplant.com

Key Findings

We analyzed Ashitabaplant.com page load time and found that the first response time was 220 ms and then it took 21.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

ashitabaplant.com performance score

39

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value18.8 s

0/100

25%

SI (Speed Index)

Value6.3 s

41/100

10%

TBT (Total Blocking Time)

Value530 ms

55/100

30%

CLS (Cumulative Layout Shift)

Value0.222

56/100

15%

TTI (Time to Interactive)

Value8.1 s

41/100

10%

Network Requests Diagram

www.ashitabaplant.com

220 ms

wp-emoji-release.min.js

61 ms

flexslider.css

18 ms

font-awesome.min.css

105 ms

style.css

19 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 69% of them (33 requests) were addressed to the original Ashitabaplant.com, 8% (4 requests) were made to Fonts.googleapis.com and 8% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (20.5 sec) relates to the external source .

Page Optimization Overview & Recommendations

Page size can be reduced by 492.0 kB (18%)

Content Size

2.8 MB

After Optimization

2.3 MB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-84%

Potential reduce by 83.8 kB

  • Original 99.7 kB
  • After minification 91.4 kB
  • After compression 15.8 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 83.8 kB or 84% of the original size.

Image Optimization

-15%

Potential reduce by 408.1 kB

  • Original 2.7 MB
  • After minification 2.2 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. Obviously, Ashitaba Plant needs image optimization as it can save up to 408.1 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 50 B

  • Original 21.0 kB
  • After minification 21.0 kB
  • After compression 20.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.

Requests Breakdown

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

Requests Now

39

After Optimization

21

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.ashitabaplant.com

www.ashitabaplant.com

220 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

61 ms

flexslider.css

flexslider.css

18 ms

font-awesome.min.css

font-awesome.min.css

105 ms

style.css

style.css

19 ms

responsive.css

responsive.css

64 ms

jquery.js

jquery.js

131 ms

jquery-migrate.min.js

jquery-migrate.min.js

96 ms

customscript.js

customscript.js

102 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

103 ms

css

css

20 ms

pm_bootstrap.css

pm_bootstrap.css

169 ms

pm_btn_style.css

pm_btn_style.css

166 ms

style.css

style.css

108 ms

css

css

21 ms

css

css

21 ms

font-awesome.min.css

font-awesome.min.css

22 ms

wp-embed.min.js

wp-embed.min.js

163 ms

frontend.js

frontend.js

161 ms

AshitabaPlantLogo-300x300.jpg

AshitabaPlantLogo-300x300.jpg

20499 ms

analytics.js

analytics.js

18 ms

fbevents.js

fbevents.js

68 ms

nobg.png

nobg.png

77 ms

ashitaba-infographic-390x250.jpg

ashitaba-infographic-390x250.jpg

142 ms

Seeds-115x115.jpg

Seeds-115x115.jpg

75 ms

Vs.-115x115.jpg

Vs.-115x115.jpg

77 ms

all-about-ashitaba-115x115.jpg

all-about-ashitaba-115x115.jpg

76 ms

Seeds-390x250.jpg

Seeds-390x250.jpg

149 ms

Vs.-390x250.jpg

Vs.-390x250.jpg

154 ms

all-about-ashitaba-390x250.jpg

all-about-ashitaba-390x250.jpg

149 ms

5-Facts-390x250.jpg

5-Facts-390x250.jpg

150 ms

ashitaba-loose-weight-390x250.jpg

ashitaba-loose-weight-390x250.jpg

148 ms

insights-390x250.jpg

insights-390x250.jpg

148 ms

digestion-mouth-390x250.gif

digestion-mouth-390x250.gif

196 ms

ashitaba-390x250.jpg

ashitaba-390x250.jpg

176 ms

Ashitaba-for-Constipation-390x250.jpg

Ashitaba-for-Constipation-390x250.jpg

177 ms

kenko-skyscaper.jpg

kenko-skyscaper.jpg

207 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

59 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

59 ms

css

css

57 ms

collect

collect

94 ms

kenko-open.jpg

kenko-open.jpg

258 ms

check.png

check.png

110 ms

1f642.png

1f642.png

46 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

122 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

10 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

22 ms

js

js

72 ms

Accessibility Review

ashitabaplant.com accessibility score

55

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

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

ashitabaplant.com best practices score

75

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

SEO Factors

ashitabaplant.com SEO score

86

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

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

ashitabaplant.com

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