Tools & Wizards About Us
kanyon.com screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

kanyon.com

kanyon.com | Evergreen.com

Page Load Speed

3.8 sec in total

First Response

65 ms

Resources Loaded

3.1 sec

Page Rendered

651 ms

kanyon.com screenshot

About Website

Click here to check amazing Kanyon content. Otherwise, check out these important facts you probably never knew about kanyon.com

Visit kanyon.com

Key Findings

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

Performance Metrics

kanyon.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.0 s

100/100

10%

LCP (Largest Contentful Paint)

Value1.0 s

100/100

25%

SI (Speed Index)

Value4.1 s

79/100

10%

TBT (Total Blocking Time)

Value2,720 ms

3/100

30%

CLS (Cumulative Layout Shift)

Value0.219

57/100

15%

TTI (Time to Interactive)

Value5.4 s

72/100

10%

Network Requests Diagram

kanyon.com

65 ms

kanyon-com

440 ms

wp-emoji-release.min.js

71 ms

styles.css

131 ms

slick.css

188 ms

Our browser made a total of 102 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Kanyon.com, 42% (43 requests) were made to Evergreen.com and 42% (43 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (802 ms) relates to the external source Google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 70.7 kB (17%)

Content Size

408.0 kB

After Optimization

337.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Kanyon.com main page is 408.0 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. 80% 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. Javascripts take 171.4 kB which makes up the majority of the site volume.

HTML Optimization

-73%

Potential reduce by 18.3 kB

  • Original 25.2 kB
  • After minification 24.1 kB
  • After compression 6.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 18.3 kB or 73% of the original size.

Image Optimization

-16%

Potential reduce by 24.5 kB

  • Original 151.3 kB
  • After minification 126.8 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. Obviously, Kanyon needs image optimization as it can save up to 24.5 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-13%

Potential reduce by 21.4 kB

  • Original 171.4 kB
  • After minification 170.8 kB
  • After compression 149.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 21.4 kB or 13% of the original size.

CSS Optimization

-11%

Potential reduce by 6.5 kB

  • Original 60.2 kB
  • After minification 59.5 kB
  • After compression 53.7 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. Kanyon.com needs all CSS files to be minified and compressed as it can save up to 6.5 kB or 11% of the original size.

Requests Breakdown

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

Requests Now

52

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

kanyon.com

kanyon.com

65 ms

kanyon-com

kanyon-com

440 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

71 ms

styles.css

styles.css

131 ms

slick.css

slick.css

188 ms

slick-theme.css

slick-theme.css

188 ms

animate.css

animate.css

194 ms

intlTelInput.css

intlTelInput.css

196 ms

ion.rangeSlider.min.css

ion.rangeSlider.min.css

212 ms

justifiedGallery.min.css

justifiedGallery.min.css

213 ms

evergreen.css

evergreen.css

312 ms

style.css

style.css

247 ms

jquery-3.3.1.min.js

jquery-3.3.1.min.js

323 ms

jquery-migrate-3.0.0.min.js

jquery-migrate-3.0.0.min.js

254 ms

js

js

105 ms

webfont.js

webfont.js

86 ms

widget.js

widget.js

123 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

269 ms

wp-polyfill.min.js

wp-polyfill.min.js

272 ms

index.js

index.js

303 ms

TweenMax.min.js

TweenMax.min.js

444 ms

html5.js

html5.js

422 ms

html-ie.js

html-ie.js

422 ms

slick.js

slick.js

656 ms

wow.min.js

wow.min.js

438 ms

intlTelInput.js

intlTelInput.js

439 ms

masonry.pkgd.min.js

masonry.pkgd.min.js

439 ms

jquery.justifiedGallery.min.js

jquery.justifiedGallery.min.js

437 ms

imagesloaded.pkgd.min.js

imagesloaded.pkgd.min.js

648 ms

ion.rangeSlider.min.js

ion.rangeSlider.min.js

651 ms

evergreen.js

evergreen.js

652 ms

api.js

api.js

92 ms

index.js

index.js

649 ms

wp-embed.min.js

wp-embed.min.js

649 ms

css

css

289 ms

logo-marketplace.svg

logo-marketplace.svg

369 ms

logo.svg

logo.svg

388 ms

tracking.js

tracking.js

477 ms

analytics.js

analytics.js

149 ms

kanyon-com-scaled.jpg

kanyon-com-scaled.jpg

299 ms

tag-white-shape.svg

tag-white-shape.svg

122 ms

arrow-white.svg

arrow-white.svg

145 ms

right-arrow.svg

right-arrow.svg

142 ms

twitter.svg

twitter.svg

254 ms

facebook.svg

facebook.svg

252 ms

linkedin.svg

linkedin.svg

250 ms

Poppins-Light.woff

Poppins-Light.woff

410 ms

Poppins-Regular.woff

Poppins-Regular.woff

326 ms

Poppins-Medium.woff

Poppins-Medium.woff

409 ms

Poppins-SemiBold.woff

Poppins-SemiBold.woff

409 ms

Poppins-Bold.woff

Poppins-Bold.woff

410 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58a-xw.ttf

241 ms

7cH1v4okm5zmbvwkAx_sfcEuiD8jvvKsOdC6.ttf

7cH1v4okm5zmbvwkAx_sfcEuiD8jvvKsOdC6.ttf

235 ms

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

1Ptxg8zYS_SKggPN4iEgvnHyvveLxVvaorCIPrQ.ttf

235 ms

neILzCirqoswsqX9zoKmNg.ttf

neILzCirqoswsqX9zoKmNg.ttf

319 ms

QGYpz_kZZAGCONcK2A4bGOj8mNhI.ttf

QGYpz_kZZAGCONcK2A4bGOj8mNhI.ttf

320 ms

gokuH6ztGkFjWe58hBNTSw.ttf

gokuH6ztGkFjWe58hBNTSw.ttf

236 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

272 ms

TK3iWkUbAhopmrd2GT8D.ttf

TK3iWkUbAhopmrd2GT8D.ttf

273 ms

UqyVK80NJXN4zfRgbdfbo55cUg.ttf

UqyVK80NJXN4zfRgbdfbo55cUg.ttf

271 ms

XLYkIZL7aopJVbZJHDuoOulC.ttf

XLYkIZL7aopJVbZJHDuoOulC.ttf

316 ms

buE3poKgYNLy0F3sWUFp.ttf

buE3poKgYNLy0F3sWUFp.ttf

334 ms

ll8lK2CWTjuqAsXDqlnIbMNs5R4dpRU.ttf

ll8lK2CWTjuqAsXDqlnIbMNs5R4dpRU.ttf

332 ms

neIWzD2ms4wxr6GvjeD0X88SHPyX2xYOoguK.ttf

neIWzD2ms4wxr6GvjeD0X88SHPyX2xYOoguK.ttf

333 ms

k3kUo8kEI-tA1RRcTZGmTlHGCaI.ttf

k3kUo8kEI-tA1RRcTZGmTlHGCaI.ttf

329 ms

Qw3fZQZaHCLgIWa29ZBbNsIE.ttf

Qw3fZQZaHCLgIWa29ZBbNsIE.ttf

333 ms

XLYgIZbkc4JPUL5CVArUVL0ntnAOTQ.ttf

XLYgIZbkc4JPUL5CVArUVL0ntnAOTQ.ttf

333 ms

ptRRTi-cavZOGqCvnNJDl5m5XmN_qs42.ttf

ptRRTi-cavZOGqCvnNJDl5m5XmN_qs42.ttf

340 ms

BCanqZABrez54xYp_M0.ttf

BCanqZABrez54xYp_M0.ttf

340 ms

l7gdbjpo0cum0ckerWCdlg_L.ttf

l7gdbjpo0cum0ckerWCdlg_L.ttf

338 ms

i7dOIFdlayuLUvgoFvHQFVZbYFI.ttf

i7dOIFdlayuLUvgoFvHQFVZbYFI.ttf

339 ms

a8IbNovtLWfR7T7bMJwrA4KU.ttf

a8IbNovtLWfR7T7bMJwrA4KU.ttf

338 ms

mem4YaWwznmLx-lzGfN7MdRyRc9MAg.ttf

mem4YaWwznmLx-lzGfN7MdRyRc9MAg.ttf

343 ms

3y9n6bU9bTPg4m8NDy3Kq24UA31gmw.ttf

3y9n6bU9bTPg4m8NDy3Kq24UA31gmw.ttf

346 ms

xMQXuF1KTa6EvGx9bp-wAX4.ttf

xMQXuF1KTa6EvGx9bp-wAX4.ttf

347 ms

zOL64pLDlL1D99S8g8PtiKchq-dmiA.ttf

zOL64pLDlL1D99S8g8PtiKchq-dmiA.ttf

344 ms

vEFV2_5QCwIS4_Dhez5jcWBuT0g.ttf

vEFV2_5QCwIS4_Dhez5jcWBuT0g.ttf

344 ms

OpNCnoEEmtHa6GcOrgs.ttf

OpNCnoEEmtHa6GcOrgs.ttf

510 ms

pxiHypAnsdxUm159X4D5V1s.ttf

pxiHypAnsdxUm159X4D5V1s.ttf

510 ms

Fh4uPib9Iyv2ucM6pGQMWimMp004La2Ceg.ttf

Fh4uPib9Iyv2ucM6pGQMWimMp004La2Ceg.ttf

510 ms

raxkHiKPvt8CMH6ZWP8PdlEq71rf0T4.ttf

raxkHiKPvt8CMH6ZWP8PdlEq71rf0T4.ttf

510 ms

9Bt33CxNwt7aOctW2xjbCstzwVKsIBVV--SjxbI.ttf

9Bt33CxNwt7aOctW2xjbCstzwVKsIBVV--SjxbI.ttf

511 ms

VdGeAZQPEpYfmHglGWsxDA.ttf

VdGeAZQPEpYfmHglGWsxDA.ttf

509 ms

QldNNTtLsx4E__B0XQmWaXk.ttf

QldNNTtLsx4E__B0XQmWaXk.ttf

548 ms

Ktk1ALSLW8zDe0rthJysWrnLsAzHEKOd.ttf

Ktk1ALSLW8zDe0rthJysWrnLsAzHEKOd.ttf

550 ms

zrfm0H3Lx-P2Xvs2ArDfBio.ttf

zrfm0H3Lx-P2Xvs2ArDfBio.ttf

547 ms

4C_yLiLzHLn_suV0mhBUPDnwt-8.ttf

4C_yLiLzHLn_suV0mhBUPDnwt-8.ttf

546 ms

collect

collect

92 ms

recaptcha__en.js

recaptcha__en.js

229 ms

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMDrMfJQ.ttf

1Pt_g8LJRfWJmhDAuUsSQamb1W0lwk4S4WjMDrMfJQ.ttf

329 ms

2EbgL-1mD1Rnb0OGKudbk0yJqNZv.ttf

2EbgL-1mD1Rnb0OGKudbk0yJqNZv.ttf

334 ms

qFdH35Wah5htUhV75VGlU94.ttf

qFdH35Wah5htUhV75VGlU94.ttf

332 ms

LYjNdG7kmE0gfaN9oA.ttf

LYjNdG7kmE0gfaN9oA.ttf

317 ms

anchor

anchor

113 ms

styles__ltr.css

styles__ltr.css

18 ms

recaptcha__en.js

recaptcha__en.js

22 ms

webworker.js

webworker.js

802 ms

logo_48.png

logo_48.png

218 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

36 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

23 ms

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

KFOlCnqEu92Fr1MmYUtfBBc9.ttf

158 ms

recaptcha__en.js

recaptcha__en.js

166 ms

Accessibility Review

kanyon.com accessibility score

63

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

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

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

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

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

kanyon.com SEO score

83

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Page is blocked from indexing

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 doesn't use 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 Kanyon.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 Kanyon.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

kanyon.com

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