Report Summary

  • 56

    Performance

    Renders faster than
    73% of other websites

  • 51

    Accessibility

    Visual factors better than
    that of 21% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 75

    SEO

    Google-friendlier than
    32% of websites

fan178.com

欧美国产日韩久久mv_无码gogo大胆啪啪艺术_老头把我添高潮了_国产成人香港三级录像视频

Page Load Speed

54.6 sec in total

First Response

3.1 sec

Resources Loaded

51 sec

Page Rendered

463 ms

fan178.com screenshot

About Website

Visit fan178.com now to see the best up-to-date Fan 178 content and also check out these interesting facts you probably never knew about fan178.com

两个奶头被吃高潮视频_无码gogo大胆啪啪艺术_老头把我添高潮了_国产成人香港三级录像视频_国产高清午夜人成在线观看_美女张开腿露出尿口扒开来摸_正在播放和哺乳期妇女做爰

Visit fan178.com

Key Findings

We analyzed Fan178.com page load time and found that the first response time was 3.1 sec and then it took 51.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 14 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

fan178.com performance score

56

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.6 s

14/100

10%

LCP (Largest Contentful Paint)

Value7.3 s

4/100

25%

SI (Speed Index)

Value5.3 s

58/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.8 s

35/100

10%

Network Requests Diagram

fan178.com

3098 ms

style.css

12870 ms

jquery-1.8.0.js

9438 ms

wb.js

63 ms

sianWeiBo.js

986 ms

Our browser made a total of 116 requests to load all elements on the main page. We found that 86% of them (100 requests) were addressed to the original Fan178.com, 2% (2 requests) were made to Oz.cnzz.com and 2% (2 requests) were made to Cnzz.mmstat.com. The less responsive or slowest element that took the longest time to load (20.5 sec) belongs to the original domain Fan178.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 501.4 kB (67%)

Content Size

744.0 kB

After Optimization

242.6 kB

In fact, the total size of Fan178.com main page is 744.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 418.2 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 102.7 kB

  • Original 114.8 kB
  • After minification 71.2 kB
  • After compression 12.1 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 43.7 kB, which is 38% 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 102.7 kB or 89% of the original size.

Image Optimization

-14%

Potential reduce by 22.2 kB

  • Original 153.8 kB
  • After minification 131.6 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, Fan 178 needs image optimization as it can save up to 22.2 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-79%

Potential reduce by 329.6 kB

  • Original 418.2 kB
  • After minification 287.6 kB
  • After compression 88.7 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 329.6 kB or 79% of the original size.

CSS Optimization

-82%

Potential reduce by 46.9 kB

  • Original 57.1 kB
  • After minification 50.6 kB
  • After compression 10.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. Fan178.com needs all CSS files to be minified and compressed as it can save up to 46.9 kB or 82% of the original size.

Requests Breakdown

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

Requests Now

99

After Optimization

84

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

Accessibility Review

fan178.com accessibility score

51

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.

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

Definition list items are not wrapped in <dl> elements

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

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

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

fan178.com SEO score

75

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

Language and Encoding

  • Language Detected

    ZH

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fan178.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Fan178.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 description is not detected on the main page of Fan 178. 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: