Tools & Wizards About Us
yakaya.com screenshot

Report Summary

  • 51

    Performance

    Renders faster than
    69% of other websites

  • 99

    Accessibility

    Visual factors better than
    that of 96% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

yakaya.com

Page Load Speed

1.2 sec in total

First Response

61 ms

Resources Loaded

667 ms

Page Rendered

455 ms

yakaya.com screenshot

About Website

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

Forsale Lander

Visit yakaya.com

Key Findings

We analyzed Yakaya.com page load time and found that the first response time was 61 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

yakaya.com performance score

51

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.8 s

57/100

10%

LCP (Largest Contentful Paint)

Value3.3 s

70/100

25%

SI (Speed Index)

Value4.9 s

66/100

10%

TBT (Total Blocking Time)

Value1,720 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.5 s

30/100

10%

Network Requests Diagram

yakaya.com

61 ms

yakaya.com

142 ms

uxcore2.min.css

94 ms

noheader.min.css

127 ms

6116094e92ec0171.css

45 ms

Our browser made a total of 27 requests to load all elements on the main page. We found that 4% of them (1 request) were addressed to the original Yakaya.com, 59% (16 requests) were made to Afternic.com and 26% (7 requests) were made to Img6.wsimg.com. The less responsive or slowest element that took the longest time to load (327 ms) relates to the external source Ds-aksb-a.akamaihd.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 66.4 kB (46%)

Content Size

144.7 kB

After Optimization

78.3 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Yakaya.com main page is 144.7 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. 50% of websites need less resources to load. HTML takes 102.5 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 62.2 kB

  • Original 102.5 kB
  • After minification 102.4 kB
  • After compression 40.3 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 62.2 kB or 61% of the original size.

JavaScript Optimization

-8%

Potential reduce by 388 B

  • Original 4.8 kB
  • After minification 4.8 kB
  • After compression 4.4 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 3.8 kB

  • Original 37.3 kB
  • After minification 37.1 kB
  • After compression 33.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. Yakaya.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 23 (92%)

Requests Now

25

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

yakaya.com

yakaya.com

61 ms

yakaya.com

yakaya.com

142 ms

uxcore2.min.css

uxcore2.min.css

94 ms

noheader.min.css

noheader.min.css

127 ms

6116094e92ec0171.css

6116094e92ec0171.css

45 ms

f3d7d266c35baf54.css

f3d7d266c35baf54.css

73 ms

8210b14763457e23.css

8210b14763457e23.css

108 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

98 ms

webpack-20b6a7dac850dbb3.js

webpack-20b6a7dac850dbb3.js

55 ms

main-999f8182f179b553.js

main-999f8182f179b553.js

61 ms

framework-f7ba292b22b03fed.js

framework-f7ba292b22b03fed.js

54 ms

_app-4df5320ba9e82638.js

_app-4df5320ba9e82638.js

97 ms

670-e807ace496afef9f.js

670-e807ace496afef9f.js

208 ms

878-f974ad59585aaeb8.js

878-f974ad59585aaeb8.js

96 ms

787-3cf420b3b3925473.js

787-3cf420b3b3925473.js

207 ms

%5Bdomain%5D-61c714b520d2a5e4.js

%5Bdomain%5D-61c714b520d2a5e4.js

207 ms

_buildManifest.js

_buildManifest.js

207 ms

_ssgManifest.js

_ssgManifest.js

207 ms

_middlewareManifest.js

_middlewareManifest.js

190 ms

polyfill.min.js

polyfill.min.js

190 ms

uxcore2.min.js

uxcore2.min.js

108 ms

vendor~uxcore2.min.js

vendor~uxcore2.min.js

207 ms

heartbeat.js

heartbeat.js

204 ms

noheader.min.js

noheader.min.js

148 ms

MCB7T-RXHNH-PGQRJ-J6HWP-UGRWC

MCB7T-RXHNH-PGQRJ-J6HWP-UGRWC

260 ms

aksb.min.js

aksb.min.js

327 ms

utag.js

utag.js

257 ms

Accessibility Review

yakaya.com accessibility score

99

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

High

Missing source maps for large first-party JavaScript

SEO Factors

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

High

robots.txt is not valid

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Yakaya.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Yakaya.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

yakaya.com

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