Tools & Wizards About Us
whoje.com screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

whoje.com

Page Load Speed

3 sec in total

First Response

64 ms

Resources Loaded

2.8 sec

Page Rendered

203 ms

whoje.com screenshot

About Website

Visit whoje.com now to see the best up-to-date Whoje content for Turkey and also check out these interesting facts you probably never knew about whoje.com

ONCE UPON A TIME... IN HOLLYWOOD is NOW PLAYING and can be found to Rent or Buy here: https://bit.ly/3nZFMYbA faded television actor and his stunt double str...

Visit whoje.com

Key Findings

We analyzed Whoje.com page load time and found that the first response time was 64 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

whoje.com performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

71/100

25%

SI (Speed Index)

Value7.7 s

24/100

10%

TBT (Total Blocking Time)

Value1,360 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.3 s

15/100

10%

Network Requests Diagram

whoje.com

64 ms

watch

609 ms

web-animations-next-lite.min.js

75 ms

webcomponents-all-noPatch.js

65 ms

fetch-polyfill.js

59 ms

Our browser made a total of 29 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Whoje.com, 62% (18 requests) were made to Youtube.com and 14% (4 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Accounts.google.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 964.2 kB (81%)

Content Size

1.2 MB

After Optimization

230.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Whoje.com main page is 1.2 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. HTML takes 670.2 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 558.6 kB

  • Original 670.2 kB
  • After minification 670.2 kB
  • After compression 111.6 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 558.6 kB or 83% of the original size.

JavaScript Optimization

-60%

Potential reduce by 87.9 kB

  • Original 147.2 kB
  • After minification 146.2 kB
  • After compression 59.3 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 87.9 kB or 60% of the original size.

CSS Optimization

-84%

Potential reduce by 317.7 kB

  • Original 376.8 kB
  • After minification 376.5 kB
  • After compression 59.0 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. Whoje.com needs all CSS files to be minified and compressed as it can save up to 317.7 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (85%)

Requests Now

20

After Optimization

3

  • AJAX
  • JavaScript
  • CSS

The browser has sent 20 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Whoje. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

whoje.com

whoje.com

64 ms

watch

watch

609 ms

web-animations-next-lite.min.js

web-animations-next-lite.min.js

75 ms

webcomponents-all-noPatch.js

webcomponents-all-noPatch.js

65 ms

fetch-polyfill.js

fetch-polyfill.js

59 ms

intersection-observer.min.js

intersection-observer.min.js

50 ms

scheduler.js

scheduler.js

33 ms

www-i18n-constants.js

www-i18n-constants.js

85 ms

css2

css2

129 ms

www-player.css

www-player.css

99 ms

www-main-desktop-watch-page-skeleton.css

www-main-desktop-watch-page-skeleton.css

88 ms

www-main-desktop-player-skeleton.css

www-main-desktop-player-skeleton.css

88 ms

www-onepick.css

www-onepick.css

87 ms

rs=AGKMywEez2_fIIumWLzNPVk7LdZV-UObkw

rs=AGKMywEez2_fIIumWLzNPVk7LdZV-UObkw

215 ms

base.js

base.js

166 ms

spf.js

spf.js

6 ms

network.js

network.js

7 ms

desktop_polymer_legacy_browsers.js

desktop_polymer_legacy_browsers.js

745 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

333 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

396 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

412 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

415 ms

offline.js

offline.js

257 ms

ServiceLogin

ServiceLogin

1397 ms

ad_status.js

ad_status.js

1361 ms

get

get

115 ms

identifier

identifier

383 ms

Create

Create

33 ms

VM1LbcxuQZ7urdjSm15-Kft2IdlldgxYJTjOL3p1Mjw.js

VM1LbcxuQZ7urdjSm15-Kft2IdlldgxYJTjOL3p1Mjw.js

36 ms

Accessibility Review

whoje.com accessibility score

68

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-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

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

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

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

whoje.com best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

whoje.com SEO score

93

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

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

    N/A

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whoje.com can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is English. Our system also found out that Whoje.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

whoje.com

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