Tools & Wizards About Us
facecast.net screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 52

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 84

    SEO

    Google-friendlier than
    53% of websites

facecast.net

Facecast — онлайн трансляции, вебинары и видеохостинг

Page Load Speed

266.9 sec in total

First Response

319 ms

Resources Loaded

265.8 sec

Page Rendered

813 ms

facecast.net screenshot

About Website

Welcome to facecast.net homepage info - get ready to check Facecast best content for Russia right away, or after learning these important things about facecast.net

Профессиональная стриминговая платформа, оборудование для онлайн-трансляций конференций, вебинаров, ивентов, мастер-классов и видеохостинг.

Visit facecast.net

Key Findings

We analyzed Facecast.net page load time and found that the first response time was 319 ms and then it took 266.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster. Unfortunately, there were 2 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

facecast.net performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value8.5 s

0/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value17.8 s

0/100

10%

TBT (Total Blocking Time)

Value31,830 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.194

63/100

15%

TTI (Time to Interactive)

Value51.5 s

0/100

10%

Network Requests Diagram

facecast.net

319 ms

1708 ms

css

44 ms

global.styles.min.css

248 ms

custom.css

373 ms

Our browser made a total of 105 requests to load all elements on the main page. We found that 70% of them (74 requests) were addressed to the original Facecast.net, 4% (4 requests) were made to Mc.yandex.com and 3% (3 requests) were made to Code.jivosite.com. The less responsive or slowest element that took the longest time to load (260.1 sec) relates to the external source Mc.yandex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 247.8 kB (19%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Facecast.net main page is 1.3 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. 70% of websites need less resources to load. Images take 939.7 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 89.8 kB

  • Original 105.8 kB
  • After minification 79.7 kB
  • After compression 16.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. This page needs HTML code to be minified as it can gain 26.1 kB, which is 25% 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 89.8 kB or 85% of the original size.

Image Optimization

-15%

Potential reduce by 143.7 kB

  • Original 939.7 kB
  • After minification 796.0 kB

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, Facecast needs image optimization as it can save up to 143.7 kB or 15% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-4%

Potential reduce by 9.0 kB

  • Original 211.1 kB
  • After minification 211.1 kB
  • After compression 202.1 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

-8%

Potential reduce by 5.3 kB

  • Original 63.6 kB
  • After minification 63.6 kB
  • After compression 58.3 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. Facecast.net has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 50 (52%)

Requests Now

96

After Optimization

46

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

facecast.net

facecast.net

319 ms

1708 ms

css

css

44 ms

global.styles.min.css

global.styles.min.css

248 ms

custom.css

custom.css

373 ms

style.css

style.css

369 ms

support.css

support.css

373 ms

aboutPlatform.css

aboutPlatform.css

377 ms

onlineTranslations.css

onlineTranslations.css

375 ms

videohosting.css

videohosting.css

392 ms

solutions.css

solutions.css

536 ms

move-to-1.8.3.min.js

move-to-1.8.3.min.js

536 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

663 ms

object-fit-polyfill-2.3.0.min.js

object-fit-polyfill-2.3.0.min.js

545 ms

hc-sticky-2.2.3.min.js

hc-sticky-2.2.3.min.js

544 ms

jquery.slick-1.9.0.min.js

jquery.slick-1.9.0.min.js

551 ms

isotope-3.0.6.min.js

isotope-3.0.6.min.js

654 ms

jquery.readmore-3.0.0.min.js

jquery.readmore-3.0.0.min.js

655 ms

jquery.form-validator.min.js

jquery.form-validator.min.js

686 ms

jquery.izimodal-1.6.0.min.js

jquery.izimodal-1.6.0.min.js

690 ms

form-action.js

form-action.js

695 ms

mail-send.js

mail-send.js

774 ms

global.scripts.min.js

global.scripts.min.js

773 ms

script.js

script.js

782 ms

popper.js

popper.js

797 ms

tippy.js

tippy.js

797 ms

jquery.inputmask.js

jquery.inputmask.js

933 ms

jquery.query.js

jquery.query.js

893 ms

4W7VsLmb7D

4W7VsLmb7D

147 ms

common.js

common.js

903 ms

aos-2.3.4.min.js

aos-2.3.4.min.js

903 ms

wp-embed.min.js

wp-embed.min.js

915 ms

social-likes.min.js

social-likes.min.js

73 ms

js

js

77 ms

gtm.js

gtm.js

59 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

846 ms

ga.js

ga.js

28 ms

conversion_async.js

conversion_async.js

67 ms

__utm.gif

__utm.gif

13 ms

collect

collect

38 ms

36 ms

ga-audiences

ga-audiences

40 ms

36 ms

logo-1.svg

logo-1.svg

134 ms

logo-white.svg

logo-white.svg

130 ms

icon3.svg

icon3.svg

216 ms

container.svg

container.svg

213 ms

menuIcon_1.svg

menuIcon_1.svg

133 ms

Content.svg

Content.svg

210 ms

Content_charity.svg

Content_charity.svg

339 ms

Content4.svg

Content4.svg

341 ms

menuIcon_2.svg

menuIcon_2.svg

344 ms

menuIcon_4.svg

menuIcon_4.svg

346 ms

menuIcon_6.svg

menuIcon_6.svg

347 ms

menuIcon_7.svg

menuIcon_7.svg

341 ms

menuIcon_8.svg

menuIcon_8.svg

443 ms

menuIcon_9.svg

menuIcon_9.svg

441 ms

loudW2.svg

loudW2.svg

461 ms

Player-3-2-1.jpeg

Player-3-2-1.jpeg

583 ms

Player-1-2.jpeg

Player-1-2.jpeg

444 ms

Player-2-2-1.jpeg

Player-2-2-1.jpeg

447 ms

Code2.png

Code2.png

809 ms

devs_2.png

devs_2.png

807 ms

Player-4-1-1.jpeg

Player-4-1-1.jpeg

690 ms

devs_4.png

devs_4.png

817 ms

playerIcon_1.svg

playerIcon_1.svg

594 ms

playerIcon_2.svg

playerIcon_2.svg

703 ms

playerIcon_3.svg

playerIcon_3.svg

722 ms

playerIcon_4.svg

playerIcon_4.svg

810 ms

Player-5-2.jpeg

Player-5-2.jpeg

946 ms

Player-6-1.jpeg

Player-6-1.jpeg

973 ms

Player-7-1.jpeg

Player-7-1.jpeg

928 ms

Player-8-1.jpeg

Player-8-1.jpeg

934 ms

Player-9-1.jpeg

Player-9-1.jpeg

934 ms

logo-1.svg

logo-1.svg

939 ms

telegramGray.png

telegramGray.png

1232 ms

telegramBlue.svg

telegramBlue.svg

1235 ms

vk.svg

vk.svg

1234 ms

init

init

616 ms

payments.png

payments.png

1232 ms

4W7VsLmb7D

4W7VsLmb7D

47 ms

4W7VsLmb7D

4W7VsLmb7D

763 ms

triangle.svg

triangle.svg

1115 ms

arr.svg

arr.svg

1111 ms

museosans-medium.otf

museosans-medium.otf

1285 ms

tag.js

tag.js

888 ms

api.min.js

api.min.js

366 ms

js

js

131 ms

museosans-300.otf

museosans-300.otf

1206 ms

museosans-bold.otf

museosans-bold.otf

1093 ms

analytics.js

analytics.js

115 ms

simple-menu.svg

simple-menu.svg

1029 ms

rtrg

rtrg

527 ms

jivosite.js

jivosite.js

1087 ms

title.svg

title.svg

936 ms

collect

collect

18 ms

collect

collect

27 ms

ga-audiences

ga-audiences

15 ms

jsconnect

jsconnect

854 ms

sync_cookie_image_check

sync_cookie_image_check

260085 ms

advert.gif

advert.gif

259961 ms

yVnjZFn8IF

yVnjZFn8IF

46 ms

pixel_identifier.js

pixel_identifier.js

854 ms

1

1

124 ms

27447396

27447396

122 ms

Accessibility Review

facecast.net accessibility score

52

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.

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

ARIA IDs are not unique

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

facecast.net 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

facecast.net 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

    RU

  • Language Claimed

    RU

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Facecast.net can be misinterpreted by Google and other search engines. Our service has detected that Russian is used on the page, and it matches the claimed language. Our system also found out that Facecast.net 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

facecast.net

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