Access funtastictoy.com. Website myaushka.ru is ready. The content is to be added

name

value

score

weighting

FCP (First Contentful Paint)

Value10.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.1 s

0/100

25%

SI (Speed Index)

Value22.8 s

0/100

10%

TBT (Total Blocking Time)

Value11,440 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.111

87/100

15%

TTI (Time to Interactive)

Value22.5 s

1/100

10%

funtastictoy.com

12 ms

www.funtastictoy.com

124 ms

css

243 ms

style.min.css

223 ms

styles.css

237 ms

Our browser made a total of 228 requests to load all elements on the main page. We found that 1% of them (2 requests) were addressed to the original Funtastictoy.com, 93% (213 requests) were made to Funtastictoy.b-cdn.net and 5% (12 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (929 ms) relates to the external source Funtastictoy.b-cdn.net.

Content Size

479.8 kB

After Optimization

66.0 kB

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

HTML Optimization

-86%

Potential reduce by 413.9 kB

Original 479.8 kB
After minification 460.8 kB
After compression 66.0 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 413.9 kB or 86% of the original size.

Requests Now

After Optimization

The browser has sent 1 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Funtastictoy. According to our analytics all requests are already optimized.

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

Areas of Improvement

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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/).

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

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