Report Summary

  • 30

    Performance

    Renders faster than
    50% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 69% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

whatweseee.com

What We Seee - Cultural Nutrition

Page Load Speed

54.5 sec in total

First Response

4.1 sec

Resources Loaded

15.4 sec

Page Rendered

35.1 sec

whatweseee.com screenshot

About Website

Visit whatweseee.com now to see the best up-to-date What We Seee content for United Arab Emirates and also check out these interesting facts you probably never knew about whatweseee.com

What We Seee, Pictures,videos, music, Style, interiors,travel and history. We are a publishing platform that will make you learn, laugh and cry. The world Curated for you. The stories you want,but nev...

Visit whatweseee.com

Key Findings

We analyzed Whatweseee.com page load time and found that the first response time was 4.1 sec and then it took 50.4 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.

Performance Metrics

whatweseee.com performance score

30

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.4 s

16/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value8.3 s

19/100

10%

TBT (Total Blocking Time)

Value390 ms

69/100

30%

CLS (Cumulative Layout Shift)

Value0.428

22/100

15%

TTI (Time to Interactive)

Value10.9 s

21/100

10%

Network Requests Diagram

www.whatweseee.com

4057 ms

wp-emoji-release.min.js

187 ms

font-awesome.min.css

128 ms

wpmm.css

131 ms

wpProQuiz_front.min.css

130 ms

Our browser made a total of 548 requests to load all elements on the main page. We found that 7% of them (38 requests) were addressed to the original Whatweseee.com, 26% (142 requests) were made to I1.wp.com and 25% (136 requests) were made to I2.wp.com. The less responsive or slowest element that took the longest time to load (4.6 sec) belongs to the original domain Whatweseee.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (4%)

Content Size

31.7 MB

After Optimization

30.4 MB

In fact, the total size of Whatweseee.com main page is 31.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. Only a small number of websites need less resources to load. Images take 30.2 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 729.6 kB

  • Original 804.7 kB
  • After minification 571.2 kB
  • After compression 75.2 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 233.5 kB, which is 29% 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 729.6 kB or 91% of the original size.

Image Optimization

-0%

Potential reduce by 71.2 kB

  • Original 30.2 MB
  • After minification 30.1 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. What We Seee images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 226.6 kB

  • Original 372.9 kB
  • After minification 355.0 kB
  • After compression 146.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 226.6 kB or 61% of the original size.

CSS Optimization

-83%

Potential reduce by 311.7 kB

  • Original 377.2 kB
  • After minification 335.4 kB
  • After compression 65.5 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. Whatweseee.com needs all CSS files to be minified and compressed as it can save up to 311.7 kB or 83% of the original size.

Requests Breakdown

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

Requests Now

540

After Optimization

448

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

Accessibility Review

whatweseee.com accessibility score

88

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

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.

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

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

SEO Factors

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

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Whatweseee.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 Whatweseee.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 data is detected on the main page of What We Seee. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: