Tools & Wizards About Us
freesee.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 85

    Accessibility

    Visual factors better than
    that of 58% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

freesee.com

Free Screen Sharing Made Easy | FreeConferenceCall.com

Page Load Speed

2.9 sec in total

First Response

138 ms

Resources Loaded

2.3 sec

Page Rendered

433 ms

freesee.com screenshot

About Website

Click here to check amazing Free See content. Otherwise, check out these important facts you probably never knew about freesee.com

Free screen sharing from FreeConferenceCall.com. Collaborate online with up to 1,000 people and screen share presentations, hold meetings with HD audio & more.

Visit freesee.com

Key Findings

We analyzed Freesee.com page load time and found that the first response time was 138 ms and then it took 2.8 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

freesee.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

51/100

25%

SI (Speed Index)

Value7.6 s

25/100

10%

TBT (Total Blocking Time)

Value2,190 ms

6/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value15.5 s

7/100

10%

Network Requests Diagram

freesee.com

138 ms

www.freescreensharing.com

155 ms

782 ms

vendor_inside-0ef4f11ba80feb7a97233767e9249172a93efd603d96b5279d888b96fc8aafc1.css

67 ms

application_wide-6933976a6be34be905276ef4b5a71e3eb36b71002220cab4b3c53c046f575664.css

134 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Freesee.com, 45% (17 requests) were made to Freeconferencecall.com and 13% (5 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (782 ms) relates to the external source Freeconferencecall.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 53.3 kB (8%)

Content Size

643.2 kB

After Optimization

590.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Freesee.com main page is 643.2 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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Javascripts take 308.7 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 38.3 kB

  • Original 50.5 kB
  • After minification 50.4 kB
  • After compression 12.3 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 38.3 kB or 76% of the original size.

Image Optimization

-0%

Potential reduce by 15 B

  • Original 153.4 kB
  • After minification 153.4 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. Free See images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 2.6 kB

  • Original 308.7 kB
  • After minification 308.7 kB
  • After compression 306.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

-9%

Potential reduce by 12.3 kB

  • Original 130.6 kB
  • After minification 130.6 kB
  • After compression 118.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. Freesee.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

29

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

freesee.com

freesee.com

138 ms

www.freescreensharing.com

www.freescreensharing.com

155 ms

782 ms

vendor_inside-0ef4f11ba80feb7a97233767e9249172a93efd603d96b5279d888b96fc8aafc1.css

vendor_inside-0ef4f11ba80feb7a97233767e9249172a93efd603d96b5279d888b96fc8aafc1.css

67 ms

application_wide-6933976a6be34be905276ef4b5a71e3eb36b71002220cab4b3c53c046f575664.css

application_wide-6933976a6be34be905276ef4b5a71e3eb36b71002220cab4b3c53c046f575664.css

134 ms

splash_pages_wide-20a469cceea8ed30a46aebe8c04dc8329a156421af9a318894ed0655ec8d6d7f.css

splash_pages_wide-20a469cceea8ed30a46aebe8c04dc8329a156421af9a318894ed0655ec8d6d7f.css

250 ms

analytics.js

analytics.js

29 ms

autopilot_sdk.js

autopilot_sdk.js

66 ms

js

js

51 ms

vendor_i18n-56bffe5f5f43a093223fc50395a74e92d9aae070c5389d7d75d0da91b17ec615.js

vendor_i18n-56bffe5f5f43a093223fc50395a74e92d9aae070c5389d7d75d0da91b17ec615.js

385 ms

en-95ef45570dfb38234c2728addff56a8acb705915229c677af50f1c1c03491a94.js

en-95ef45570dfb38234c2728addff56a8acb705915229c677af50f1c1c03491a94.js

186 ms

application_i18n-e818496916fdf4269f9b603f05aff89dc4dcc2ae28dd432cb2ad3cfd4017755f.js

application_i18n-e818496916fdf4269f9b603f05aff89dc4dcc2ae28dd432cb2ad3cfd4017755f.js

376 ms

01189290044

01189290044

197 ms

_ty1kvFAO84

_ty1kvFAO84

398 ms

freeconferencecall-logo.svg

freeconferencecall-logo.svg

181 ms

screensharing-header.jpg

screensharing-header.jpg

218 ms

sized-woman-for-education-1.jpg

sized-woman-for-education-1.jpg

218 ms

screen-share-3.jpg

screen-share-3.jpg

184 ms

group-presentation.jpg

group-presentation.jpg

218 ms

meeting-wall-bottom-8.jpg

meeting-wall-bottom-8.jpg

184 ms

collect

collect

103 ms

open-sans-v15-latin-regular.woff

open-sans-v15-latin-regular.woff

137 ms

open-sans-v18-latin-600.woff

open-sans-v18-latin-600.woff

135 ms

open-sans-v15-latin-700.woff

open-sans-v15-latin-700.woff

135 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

318 ms

collect

collect

207 ms

js

js

57 ms

ga-audiences

ga-audiences

382 ms

www-player.css

www-player.css

30 ms

www-embed-player.js

www-embed-player.js

50 ms

base.js

base.js

82 ms

ad_status.js

ad_status.js

179 ms

vD-PFjxSijoP4-I0oY5JcElr_81RPxK9SqvIhUi9qS8.js

vD-PFjxSijoP4-I0oY5JcElr_81RPxK9SqvIhUi9qS8.js

86 ms

embed.js

embed.js

40 ms

KFOmCnqEu92Fr1Mu4mxP.ttf

KFOmCnqEu92Fr1Mu4mxP.ttf

138 ms

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

KFOlCnqEu92Fr1MmEU9fBBc9.ttf

140 ms

id

id

126 ms

bat.js

bat.js

24 ms

Accessibility Review

freesee.com accessibility score

85

Accessibility Issues

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-*] attributes do not match their roles

High

[aria-*] attributes do not have valid values

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

freesee.com best practices score

83

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

Page has valid source maps

SEO Factors

freesee.com SEO score

86

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

Links do not have descriptive text

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Freesee.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 Freesee.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

freesee.com

Open Graph description is not detected on the main page of Free See. 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: