Tools & Wizards About Us
play.video screenshot

Report Summary

  • 69

    Performance

    Renders faster than
    80% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

play.video

ClickView | Educational Video Teaching Resources for Schools

Page Load Speed

2.9 sec in total

First Response

223 ms

Resources Loaded

1.2 sec

Page Rendered

1.5 sec

play.video screenshot

About Website

Click here to check amazing Play content for Russia. Otherwise, check out these important facts you probably never knew about play.video

ClickView makes it easy to find short, relevant videos to deliver engaging lessons. Used by 6,000 schools. Sign up for free and try for your classroom today.

Visit play.video

Key Findings

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

Performance Metrics

play.video performance score

69

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.5 s

34/100

10%

LCP (Largest Contentful Paint)

Value5.7 s

16/100

25%

SI (Speed Index)

Value3.5 s

88/100

10%

TBT (Total Blocking Time)

Value50 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value5.1 s

75/100

10%

Network Requests Diagram

play.video

223 ms

www.clickvieweducation.com

74 ms

6db226f5e57f2a2b.css

12 ms

b8e302d41b271438.css

24 ms

fd9d1056-02246458df112013.js

25 ms

Our browser made a total of 94 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Play.video, 99% (93 requests) were made to Clickvieweducation.com. The less responsive or slowest element that took the longest time to load (610 ms) relates to the external source Clickvieweducation.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 828.9 kB (7%)

Content Size

11.7 MB

After Optimization

10.9 MB

  • HTML
  • Images

In fact, the total size of Play.video main page is 11.7 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 11.3 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 344.9 kB

  • Original 412.0 kB
  • After minification 411.3 kB
  • After compression 67.1 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 344.9 kB or 84% of the original size.

Image Optimization

-4%

Potential reduce by 484.0 kB

  • Original 11.3 MB
  • After minification 10.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. Play images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 22 (24%)

Requests Now

92

After Optimization

70

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

play.video

play.video

223 ms

www.clickvieweducation.com

www.clickvieweducation.com

74 ms

6db226f5e57f2a2b.css

6db226f5e57f2a2b.css

12 ms

b8e302d41b271438.css

b8e302d41b271438.css

24 ms

fd9d1056-02246458df112013.js

fd9d1056-02246458df112013.js

25 ms

2472-7d8302a3f573e57c.js

2472-7d8302a3f573e57c.js

18 ms

main-app-fe8494148f0fcf10.js

main-app-fe8494148f0fcf10.js

17 ms

469-15b33bbdd362e41e.js

469-15b33bbdd362e41e.js

25 ms

1257-3e32dbe52df86b93.js

1257-3e32dbe52df86b93.js

16 ms

9294-981c66376639a6cb.js

9294-981c66376639a6cb.js

20 ms

5952-2cece8cf073a239f.js

5952-2cece8cf073a239f.js

21 ms

606-a85a51280209fc67.js

606-a85a51280209fc67.js

29 ms

3994-826ae157bfb499a0.js

3994-826ae157bfb499a0.js

29 ms

4237-1033604eadd372aa.js

4237-1033604eadd372aa.js

30 ms

8106-8e5970cf1ce3ec60.js

8106-8e5970cf1ce3ec60.js

29 ms

6462-591383661618b7cb.js

6462-591383661618b7cb.js

29 ms

8533-a8429ace603bd238.js

8533-a8429ace603bd238.js

33 ms

5702-2828c29c990f603e.js

5702-2828c29c990f603e.js

29 ms

5686-be6e895cc03c74fb.js

5686-be6e895cc03c74fb.js

38 ms

layout-2b1f97f4c5ca3036.js

layout-2b1f97f4c5ca3036.js

30 ms

not-found-b16810b17a964f67.js

not-found-b16810b17a964f67.js

33 ms

8246-4eca70108ffce30c.js

8246-4eca70108ffce30c.js

34 ms

9645-35372157a48c6b5f.js

9645-35372157a48c6b5f.js

33 ms

9191-e2a572830ff1c578.js

9191-e2a572830ff1c578.js

39 ms

page-9c094b2c2b344dac.js

page-9c094b2c2b344dac.js

37 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

39 ms

webpack-f00c59821dd62d97.js

webpack-f00c59821dd62d97.js

33 ms

image

image

41 ms

image

image

102 ms

image

image

37 ms

image

image

35 ms

image

image

74 ms

image

image

88 ms

image

image

107 ms

image

image

104 ms

image

image

73 ms

image

image

99 ms

image

image

131 ms

image

image

133 ms

image

image

143 ms

image

image

146 ms

image

image

210 ms

image

image

210 ms

image

image

248 ms

image

image

259 ms

clickview_shiny_video.51660c1f.svg

clickview_shiny_video.51660c1f.svg

146 ms

image

image

255 ms

image

image

279 ms

image

image

288 ms

image

image

300 ms

image

image

373 ms

image

image

365 ms

image

image

449 ms

image

image

402 ms

image

image

367 ms

image

image

424 ms

image

image

460 ms

clickview_engage_star.104719ea.svg

clickview_engage_star.104719ea.svg

373 ms

image

image

504 ms

image

image

380 ms

clickview_cloud_video.4d938fb6.svg

clickview_cloud_video.4d938fb6.svg

386 ms

clickview_share_svg.7c4528bb.svg

clickview_share_svg.7c4528bb.svg

415 ms

image

image

507 ms

image

image

545 ms

image

image

446 ms

image

image

515 ms

clickview_heart.0f01d8e5.svg

clickview_heart.0f01d8e5.svg

395 ms

image

image

597 ms

image

image

475 ms

image

image

513 ms

image

image

505 ms

image

image

492 ms

image

image

523 ms

image

image

492 ms

image

image

507 ms

image

image

536 ms

image

image

610 ms

image

image

530 ms

image

image

474 ms

image

image

468 ms

image

image

453 ms

image

image

517 ms

navy-wave.1c49c420.svg

navy-wave.1c49c420.svg

423 ms

image

image

465 ms

image

image

467 ms

image

image

424 ms

image

image

395 ms

image

image

394 ms

gray-wave.d64335d6.svg

gray-wave.d64335d6.svg

374 ms

image

image

440 ms

image

image

407 ms

image

image

439 ms

image

image

399 ms

image

image

383 ms

Accessibility Review

play.video accessibility score

71

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

Document doesn't have a <title> element

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

play.video 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

Browser errors were logged to the console

SEO Factors

play.video SEO score

58

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Document doesn't have a <title> element

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 Play.video 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 Play.video 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

play.video

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