Tools & Wizards About Us
fathare.com screenshot

Report Summary

  • 0

    Performance

  • 45

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

fathare.com

日韩一区二区三,日本成aⅴ人片日本伦,日本亚洲精品一区二区三,a级毛片免费在线观看

Page Load Speed

13.5 sec in total

First Response

3.6 sec

Resources Loaded

9.5 sec

Page Rendered

411 ms

fathare.com screenshot

About Website

Welcome to fathare.com homepage info - get ready to check Fathare best content right away, or after learning these important things about fathare.com

日韩一区二区三,日本成aⅴ人片日本伦,日本亚洲精品一区二区三,a级毛片免费在线观看,国产精品久久久久久不卡,亚洲午夜久久久久国产,国产精品v片在线观看不卡,国产精品久久久久久久久久久不卡,精品视频在线观看免费,国产成人一区二区三区草莓视频,一本一本久久a久久综合精品蜜桃

Visit fathare.com

Key Findings

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

Performance Metrics

fathare.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0

0/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value0

0/100

10%

TBT (Total Blocking Time)

Value0

0/100

30%

CLS (Cumulative Layout Shift)

Value0.148

76/100

15%

TTI (Time to Interactive)

Value0

0/100

10%

Network Requests Diagram

fathare.com

3573 ms

music

903 ms

common.css

1413 ms

jquery-1.8.3.min.js

1415 ms

wb.js

1023 ms

Our browser made a total of 51 requests to load all elements on the main page. We found that 16% of them (8 requests) were addressed to the original Fathare.com, 51% (26 requests) were made to Shfile.b0.upaiyun.com and 14% (7 requests) were made to Img.t.sinajs.cn. The less responsive or slowest element that took the longest time to load (3.6 sec) belongs to the original domain Fathare.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 379.0 kB (59%)

Content Size

645.0 kB

After Optimization

266.0 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Fathare.com main page is 645.0 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. 35% of websites need less resources to load. Javascripts take 400.2 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 34.5 kB

  • Original 40.5 kB
  • After minification 35.3 kB
  • After compression 6.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 5.3 kB, which is 13% 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 34.5 kB or 85% of the original size.

Image Optimization

-11%

Potential reduce by 15.1 kB

  • Original 137.4 kB
  • After minification 122.3 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, Fathare needs image optimization as it can save up to 15.1 kB or 11% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 276.6 kB

  • Original 400.2 kB
  • After minification 382.0 kB
  • After compression 123.6 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 276.6 kB or 69% of the original size.

CSS Optimization

-79%

Potential reduce by 52.8 kB

  • Original 66.8 kB
  • After minification 61.7 kB
  • After compression 14.1 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. Fathare.com needs all CSS files to be minified and compressed as it can save up to 52.8 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 23 (47%)

Requests Now

49

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

fathare.com

fathare.com

3573 ms

music

music

903 ms

common.css

common.css

1413 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1415 ms

wb.js

wb.js

1023 ms

common.js

common.js

1666 ms

login_pop.css

login_pop.css

1699 ms

login_pop.js

login_pop.js

1403 ms

index.css

index.css

1041 ms

circle.player.css

circle.player.css

1344 ms

comment.js

comment.js

442 ms

jquery.jplayer.min.js

jquery.jplayer.min.js

1464 ms

combine.js

combine.js

1063 ms

music.js

music.js

1461 ms

layer.js

layer.js

1655 ms

query

query

1323 ms

logo2.png

logo2.png

2958 ms

default.png

default.png

2620 ms

weibo_32x32.png

weibo_32x32.png

1194 ms

shuffle_dark.png

shuffle_dark.png

812 ms

shuffle.png

shuffle.png

999 ms

ruo.png

ruo.png

3527 ms

xubox_ico0.png

xubox_ico0.png

316 ms

xubox_title0.png

xubox_title0.png

430 ms

hdr.png

hdr.png

420 ms

hdr_on.png

hdr_on.png

397 ms

list.png

list.png

425 ms

bgr.jpg

bgr.jpg

523 ms

controls.jpg

controls.jpg

502 ms

shuffle_dark.png

shuffle_dark.png

595 ms

table_nav.png

table_nav.png

683 ms

heart.png

heart.png

644 ms

blue_play.png

blue_play.png

626 ms

overlay.png

overlay.png

902 ms

comments.php

comments.php

1688 ms

layer.css

layer.css

662 ms

progress.png

progress.png

672 ms

buffer.png

buffer.png

322 ms

weiboComments.css

weiboComments.css

516 ms

skin_default.css

skin_default.css

518 ms

gaea_1_19.js

gaea_1_19.js

542 ms

comment-server.js

comment-server.js

8 ms

suda.js

suda.js

7 ms

1

1

1138 ms

wb_logo16_a.png

wb_logo16_a.png

16 ms

bg_sharebox.png

bg_sharebox.png

17 ms

icon_pub.png

icon_pub.png

17 ms

btns_word.png

btns_word.png

18 ms

icon_tips.png

icon_tips.png

16 ms

a.gif

a.gif

1105 ms

z.gif

z.gif

1297 ms

Accessibility Review

fathare.com accessibility score

45

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

<frame> or <iframe> elements do not have a title

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

fathare.com best practices score

75

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

Page has valid source maps

SEO Factors

fathare.com SEO score

100

Search Engine Optimization Advices

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fathare.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) and no language is claimed in <html> or <meta> tags either. Our system also found out that Fathare.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

fathare.com

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