Tools & Wizards About Us
yolycollect.com screenshot

Report Summary

  • 13

    Performance

    Renders faster than
    25% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

yolycollect.com

YolyCollect

Page Load Speed

3.3 sec in total

First Response

227 ms

Resources Loaded

2.8 sec

Page Rendered

331 ms

yolycollect.com screenshot

About Website

Welcome to yolycollect.com homepage info - get ready to check Yoly Collect best content right away, or after learning these important things about yolycollect.com

YolyCollect

Visit yolycollect.com

Key Findings

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

Performance Metrics

yolycollect.com performance score

13

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.1 s

22/100

10%

LCP (Largest Contentful Paint)

Value37.8 s

0/100

25%

SI (Speed Index)

Value23.1 s

0/100

10%

TBT (Total Blocking Time)

Value1,050 ms

25/100

30%

CLS (Cumulative Layout Shift)

Value0.399

25/100

15%

TTI (Time to Interactive)

Value26.0 s

0/100

10%

Network Requests Diagram

yolycollect.com

227 ms

yolycollect.com

665 ms

91d3b2edceb9451f3c395d638cec8a1e.css

197 ms

js

47 ms

69a93451010f1a04c9313cdaa739bf64.js

470 ms

Our browser made a total of 59 requests to load all elements on the main page. We found that 68% of them (40 requests) were addressed to the original Yolycollect.com, 20% (12 requests) were made to Embed.tawk.to and 3% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Yolycollect.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 832.4 kB (16%)

Content Size

5.1 MB

After Optimization

4.2 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-88%

Potential reduce by 309.8 kB

  • Original 351.3 kB
  • After minification 351.3 kB
  • After compression 41.5 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 309.8 kB or 88% of the original size.

Image Optimization

-11%

Potential reduce by 498.2 kB

  • Original 4.3 MB
  • After minification 3.8 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, Yoly Collect needs image optimization as it can save up to 498.2 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-7%

Potential reduce by 24.4 kB

  • Original 325.3 kB
  • After minification 325.3 kB
  • After compression 300.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

-0%

Potential reduce by 0 B

  • Original 61.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.

Requests Breakdown

Number of requests can be reduced by 17 (34%)

Requests Now

50

After Optimization

33

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

yolycollect.com

yolycollect.com

227 ms

yolycollect.com

yolycollect.com

665 ms

91d3b2edceb9451f3c395d638cec8a1e.css

91d3b2edceb9451f3c395d638cec8a1e.css

197 ms

js

js

47 ms

69a93451010f1a04c9313cdaa739bf64.js

69a93451010f1a04c9313cdaa739bf64.js

470 ms

js

js

43 ms

4e74397ac58f2a5cf4b80564834bee2d.js

4e74397ac58f2a5cf4b80564834bee2d.js

551 ms

fbevents.js

fbevents.js

76 ms

Asset%205-2176x628.png

Asset%205-2176x628.png

219 ms

Artboard%201-768x500.png

Artboard%201-768x500.png

615 ms

Artboard%202-768x500.png

Artboard%202-768x500.png

566 ms

Artboard%203-768x500.png

Artboard%203-768x500.png

620 ms

Artboard%204-768x500.png

Artboard%204-768x500.png

965 ms

Artboard%2012-768x500.png

Artboard%2012-768x500.png

790 ms

Artboard%205-768x500.png

Artboard%205-768x500.png

983 ms

Artboard%2016-768x500.png

Artboard%2016-768x500.png

662 ms

Artboard%209-768x500.png

Artboard%209-768x500.png

711 ms

1-768x500.jpeg

1-768x500.jpeg

729 ms

2-768x500.jpeg

2-768x500.jpeg

759 ms

2-768x500.png

2-768x500.png

807 ms

4-768x500.jpeg

4-768x500.jpeg

824 ms

1-768x500.png

1-768x500.png

854 ms

demo06-768x500.jpg

demo06-768x500.jpg

882 ms

WhatsApp%20Image%202019-09-30%20at%201.15.36%20PM-768x500.jpeg

WhatsApp%20Image%202019-09-30%20at%201.15.36%20PM-768x500.jpeg

900 ms

cms-image-1-651x650.jpg

cms-image-1-651x650.jpg

922 ms

cat-img-1-634x640.jpg

cat-img-1-634x640.jpg

951 ms

Main-Banner2-512x250.jpg

Main-Banner2-512x250.jpg

975 ms

Blue-Light-Filter-Glasses-Unisex-Nerd-Non-prescription-Clear-Lens-Fake-Glasses-B08CBR9MT5-8345-250x250.jpeg

Blue-Light-Filter-Glasses-Unisex-Nerd-Non-prescription-Clear-Lens-Fake-Glasses-B08CBR9MT5-8345-250x250.jpeg

993 ms

Blue-Light-Filter-Glasses-Unisex-Nerd-Non-prescription-Clear-Lens-Fake-Glasses-B08CBR9MT5-8-250x250.jpeg

Blue-Light-Filter-Glasses-Unisex-Nerd-Non-prescription-Clear-Lens-Fake-Glasses-B08CBR9MT5-8-250x250.jpeg

1017 ms

Blue-Light-Filter-Glasses-Unisex-Nerd-Non-prescription-Clear-Lens-Fake-Glasses-B08CBR9MT5-7596-250x250.jpeg

Blue-Light-Filter-Glasses-Unisex-Nerd-Non-prescription-Clear-Lens-Fake-Glasses-B08CBR9MT5-7596-250x250.jpeg

1045 ms

white_logo%20-2510x724.png

white_logo%20-2510x724.png

1055 ms

2-85x85.png

2-85x85.png

1066 ms

3-85x85.png

3-85x85.png

1074 ms

4-85x85.png

4-85x85.png

1086 ms

5-85x85.png

5-85x85.png

1111 ms

6-85x85.png

6-85x85.png

1140 ms

7-85x85.png

7-85x85.png

1145 ms

8-85x85.png

8-85x85.png

1159 ms

9-85x85.png

9-85x85.png

1166 ms

10-85x85.png

10-85x85.png

1177 ms

Paypal-logo-white.svg-85x85.png

Paypal-logo-white.svg-85x85.png

1205 ms

icomoon.ttf

icomoon.ttf

1199 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1185 ms

default

default

242 ms

webfont.js

webfont.js

137 ms

css

css

38 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hOA-W1Q.ttf

27 ms

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5W1Q.ttf

SLXgc1nY6HkvangtZmpQdkhzfH5lkSs2SgRjCAGMQ1z0hAc5W1Q.ttf

40 ms

twk-arr-find-polyfill.js

twk-arr-find-polyfill.js

56 ms

twk-object-values-polyfill.js

twk-object-values-polyfill.js

63 ms

twk-event-polyfill.js

twk-event-polyfill.js

80 ms

twk-entries-polyfill.js

twk-entries-polyfill.js

58 ms

twk-promise-polyfill.js

twk-promise-polyfill.js

62 ms

twk-main.js

twk-main.js

28 ms

twk-vendor.js

twk-vendor.js

48 ms

twk-chunk-vendors.js

twk-chunk-vendors.js

66 ms

twk-chunk-common.js

twk-chunk-common.js

72 ms

twk-runtime.js

twk-runtime.js

79 ms

twk-app.js

twk-app.js

79 ms

Accessibility Review

yolycollect.com accessibility score

81

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Best Practices

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

High

Page has valid source maps

SEO Factors

yolycollect.com SEO score

89

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

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

High

Tap targets are not sized appropriately

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

yolycollect.com

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