Report Summary

  • 2

    Performance

    Renders faster than
    19% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

playrobot.com

飆機器人

Page Load Speed

2.4 sec in total

First Response

555 ms

Resources Loaded

1.3 sec

Page Rendered

524 ms

playrobot.com screenshot

About Website

Welcome to playrobot.com homepage info - get ready to check Playrobot best content for Taiwan right away, or after learning these important things about playrobot.com

【追求卓越、專注成效】 我們提供卓越創新的科技與教育資源,專注各項學習與成效的發展,致力為科技播種,讓科技樂活我們的生活。 飆機器人_科技教育應用團隊

Visit playrobot.com

Key Findings

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

Performance Metrics

playrobot.com performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.1 s

9/100

10%

LCP (Largest Contentful Paint)

Value27.2 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value2,680 ms

4/100

30%

CLS (Cumulative Layout Shift)

Value1.801

0/100

15%

TTI (Time to Interactive)

Value27.6 s

0/100

10%

Network Requests Diagram

www.playrobot.com

555 ms

v_10_f376fa99ed3c7e756d06f76992f34b3b_all.css

32 ms

css

28 ms

a7f3283c161ab334a03b321ca39a6b40.jpg

20 ms

playrobot-development-logo-1444004343.jpg

15 ms

Our browser made a total of 45 requests to load all elements on the main page. We found that 84% of them (38 requests) were addressed to the original Playrobot.com, 7% (3 requests) were made to Google-analytics.com and 4% (2 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (555 ms) belongs to the original domain Playrobot.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 525.0 kB (28%)

Content Size

1.9 MB

After Optimization

1.3 MB

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

HTML Optimization

-85%

Potential reduce by 79.2 kB

  • Original 93.7 kB
  • After minification 78.6 kB
  • After compression 14.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. This page needs HTML code to be minified as it can gain 15.2 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 79.2 kB or 85% of the original size.

Image Optimization

-1%

Potential reduce by 7.2 kB

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

JavaScript Optimization

-69%

Potential reduce by 232.9 kB

  • Original 339.9 kB
  • After minification 339.9 kB
  • After compression 107.0 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 232.9 kB or 69% of the original size.

CSS Optimization

-83%

Potential reduce by 205.7 kB

  • Original 247.5 kB
  • After minification 244.0 kB
  • After compression 41.8 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. Playrobot.com needs all CSS files to be minified and compressed as it can save up to 205.7 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 3 (7%)

Requests Now

41

After Optimization

38

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

Accessibility Review

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

Best Practices

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

Missing source maps for large first-party JavaScript

SEO Factors

playrobot.com SEO score

84

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    JA

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Playrobot.com can be misinterpreted by Google and other search engines. Our service has detected that Japanese is used on the page, and it does not match the claimed Chinese language. Our system also found out that Playrobot.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 description is not detected on the main page of Playrobot. 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: