Tools & Wizards About Us
yewkart.com screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

yewkart.com

yewkart.com

Page Load Speed

3.6 sec in total

First Response

121 ms

Resources Loaded

2.5 sec

Page Rendered

1 sec

yewkart.com screenshot

About Website

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

Visit yewkart.com

Key Findings

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

yewkart.com performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value10.5 s

0/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.001

100/100

15%

TTI (Time to Interactive)

Value10.6 s

23/100

10%

Network Requests Diagram

yewkart.com

121 ms

yewkart.com

2013 ms

main.min.css

63 ms

custom-frontend-lite.min.css

80 ms

swiper.min.css

63 ms

Our browser made a total of 123 requests to load all elements on the main page. We found that 79% of them (97 requests) were addressed to the original Yewkart.com, 20% (24 requests) were made to Fonts.gstatic.com and 2% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Yewkart.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 193.2 kB (5%)

Content Size

4.1 MB

After Optimization

3.9 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-84%

Potential reduce by 189.0 kB

  • Original 224.3 kB
  • After minification 218.6 kB
  • After compression 35.2 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 189.0 kB or 84% of the original size.

Image Optimization

-0%

Potential reduce by 16 B

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

JavaScript Optimization

-0%

Potential reduce by 3.3 kB

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

CSS Optimization

-1%

Potential reduce by 829 B

  • Original 115.2 kB
  • After minification 115.2 kB
  • After compression 114.4 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. Yewkart.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 70 (73%)

Requests Now

96

After Optimization

26

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yewkart.com

yewkart.com

121 ms

yewkart.com

yewkart.com

2013 ms

main.min.css

main.min.css

63 ms

custom-frontend-lite.min.css

custom-frontend-lite.min.css

80 ms

swiper.min.css

swiper.min.css

63 ms

post-11.css

post-11.css

62 ms

global.css

global.css

63 ms

post-6.css

post-6.css

86 ms

post-293.css

post-293.css

88 ms

post-294.css

post-294.css

87 ms

sidebar-app.css

sidebar-app.css

88 ms

css2

css2

27 ms

astra-addon-65b3952405c770-75014027.css

astra-addon-65b3952405c770-75014027.css

97 ms

general.min.css

general.min.css

23 ms

text-animations.min.css

text-animations.min.css

26 ms

frontend.min.css

frontend.min.css

73 ms

all.min.css

all.min.css

28 ms

css

css

17 ms

jquery.min.js

jquery.min.js

60 ms

jquery-migrate.min.js

jquery-migrate.min.js

43 ms

Logo-1.png

Logo-1.png

21 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

50 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

50 ms

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

KFOlCnqEu92Fr1MmSU5fBBc9.ttf

55 ms

KFOkCnqEu92Fr1MmgVxIIzc.ttf

KFOkCnqEu92Fr1MmgVxIIzc.ttf

51 ms

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

KFOlCnqEu92Fr1MmWUlfBBc9.ttf

56 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

55 ms

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

pxiByp8kv8JHgFVrLGT9Z1xlEA.ttf

57 ms

pxiEyp8kv8JHgFVrJJfedw.ttf

pxiEyp8kv8JHgFVrJJfedw.ttf

57 ms

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

pxiByp8kv8JHgFVrLDz8Z1xlEA.ttf

58 ms

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

pxiByp8kv8JHgFVrLFj_Z1xlEA.ttf

65 ms

pxiGyp8kv8JHgFVrLPTucHtF.ttf

pxiGyp8kv8JHgFVrLPTucHtF.ttf

58 ms

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

pxiByp8kv8JHgFVrLEj6Z1xlEA.ttf

65 ms

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

pxiByp8kv8JHgFVrLCz7Z1xlEA.ttf

67 ms

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

pxiByp8kv8JHgFVrLDD4Z1xlEA.ttf

67 ms

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

pxiByp8kv8JHgFVrLBT5Z1xlEA.ttf

66 ms

custom-widget-icon-list.min.css

custom-widget-icon-list.min.css

53 ms

pic-11.png

pic-11.png

68 ms

pic-12.png

pic-12.png

107 ms

Google-Play.png

Google-Play.png

44 ms

App-Store.png

App-Store.png

44 ms

pic-10.jpg

pic-10.jpg

51 ms

pic-1.png

pic-1.png

129 ms

pic-8.png

pic-8.png

51 ms

pic-5.png

pic-5.png

70 ms

pic-7.png

pic-7.png

70 ms

pic-6.png

pic-6.png

82 ms

pic-3.png

pic-3.png

84 ms

pic-4.png

pic-4.png

89 ms

pic-14-1024x901.png

pic-14-1024x901.png

230 ms

custom-widget-icon-box.min.css

custom-widget-icon-box.min.css

100 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvoorCIPrQ.ttf

28 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

29 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVuEorCIPrQ.ttf

30 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtaorCIPrQ.ttf

31 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvao7CIPrQ.ttf

29 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVsEpbCIPrQ.ttf

31 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVs9pbCIPrQ.ttf

36 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtapbCIPrQ.ttf

36 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVtzpbCIPrQ.ttf

40 ms

pic-15-1024x896.png

pic-15-1024x896.png

119 ms

pic-13.png

pic-13.png

227 ms

pic-17.jpg

pic-17.jpg

118 ms

pic-16.jpg

pic-16.jpg

122 ms

Team-3.jpg

Team-3.jpg

138 ms

Team-2.jpg

Team-2.jpg

139 ms

Team-1.jpg

Team-1.jpg

142 ms

pic-2.png

pic-2.png

144 ms

wpr-link-animations.min.css

wpr-link-animations.min.css

103 ms

post-21.css

post-21.css

102 ms

loading-animations.min.css

loading-animations.min.css

106 ms

button-animations.min.css

button-animations.min.css

110 ms

animations.min.css

animations.min.css

121 ms

frontend.min.js

frontend.min.js

166 ms

particles.js

particles.js

167 ms

jarallax.min.js

jarallax.min.js

171 ms

parallax.min.js

parallax.min.js

173 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

174 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

175 ms

wp-polyfill.min.js

wp-polyfill.min.js

177 ms

react.min.js

react.min.js

175 ms

react-dom.min.js

react-dom.min.js

176 ms

hooks.min.js

hooks.min.js

177 ms

i18n.min.js

i18n.min.js

177 ms

url.min.js

url.min.js

203 ms

api-fetch.min.js

api-fetch.min.js

202 ms

dom-ready.min.js

dom-ready.min.js

203 ms

a11y.min.js

a11y.min.js

202 ms

deprecated.min.js

deprecated.min.js

200 ms

dom.min.js

dom.min.js

190 ms

escape-html.min.js

escape-html.min.js

188 ms

element.min.js

element.min.js

184 ms

is-shallow-equal.min.js

is-shallow-equal.min.js

171 ms

keycodes.min.js

keycodes.min.js

168 ms

priority-queue.min.js

priority-queue.min.js

153 ms

compose.min.js

compose.min.js

151 ms

moment.min.js

moment.min.js

150 ms

date.min.js

date.min.js

155 ms

html-entities.min.js

html-entities.min.js

148 ms

primitives.min.js

primitives.min.js

146 ms

private-apis.min.js

private-apis.min.js

144 ms

redux-routine.min.js

redux-routine.min.js

141 ms

data.min.js

data.min.js

131 ms

rich-text.min.js

rich-text.min.js

142 ms

warning.min.js

warning.min.js

137 ms

components.min.js

components.min.js

161 ms

plugins.min.js

plugins.min.js

81 ms

sidebar-app.js

sidebar-app.js

107 ms

astra-addon-65b395240a4ae1-52605238.js

astra-addon-65b395240a4ae1-52605238.js

105 ms

general.min.js

general.min.js

101 ms

imagesloaded.min.js

imagesloaded.min.js

111 ms

slick.min.js

slick.min.js

111 ms

perfect-scrollbar.min.js

perfect-scrollbar.min.js

117 ms

webpack.runtime.min.js

webpack.runtime.min.js

120 ms

frontend-modules.min.js

frontend-modules.min.js

120 ms

waypoints.min.js

waypoints.min.js

117 ms

core.min.js

core.min.js

119 ms

frontend.min.js

frontend.min.js

122 ms

frontend.min.js

frontend.min.js

136 ms

modal-popups.min.js

modal-popups.min.js

117 ms

pic-9.jpg

pic-9.jpg

112 ms

Footer.jpg

Footer.jpg

110 ms

admin-ajax.php

admin-ajax.php

39 ms

Accessibility Review

yewkart.com accessibility score

86

Accessibility Issues

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

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

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

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

yewkart.com

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