Access fangdr.com.

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value14.5 s

0/100

25%

SI (Speed Index)

Value20.6 s

0/100

10%

TBT (Total Blocking Time)

Value20 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value17.0 s

4/100

10%

fangdr.com

5298 ms

index.css

2838 ms

tab.css

1218 ms

toTop.1.0.css

1371 ms

fcqz.css

1360 ms

Our browser made a total of 140 requests to load all elements on the main page. We found that 40% of them (56 requests) were addressed to the original Fangdr.com, 53% (74 requests) were made to File.gz.fangdr.com and 1% (2 requests) were made to . The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source File.gz.fangdr.com.

Content Size

1.4 MB

After Optimization

1.1 MB

In fact, the total size of Fangdr.com main page is 1.4 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. 25% of websites need less resources to load. Images take 1.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 87.3 kB

Original 108.1 kB
After minification 101.9 kB
After compression 20.8 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 87.3 kB or 81% of the original size.

Image Optimization

-7%

Potential reduce by 69.2 kB

Original 1.0 MB
After minification 952.0 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. Fangdr images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 183.6 kB

Original 277.2 kB
After minification 260.0 kB
After compression 93.5 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 183.6 kB or 66% of the original size.

CSS Optimization

-84%

Potential reduce by 18.1 kB

Original 21.6 kB
After minification 18.0 kB
After compression 3.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. Fangdr.com needs all CSS files to be minified and compressed as it can save up to 18.1 kB or 84% of the original size.

Requests Now

113

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve keyboard navigation in your application.

High

Heading elements are not in a sequentially-descending order

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.

High

Links do not have a discernible name

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

These items highlight common accessibility best practices.

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Page has valid source maps

Search Engine Optimization Advices

To appear in search results, crawlers need access to your app.

High

Links are not crawlable

High

Page is blocked from indexing

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/).

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

fangdr.com

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

Report Summary

Performance

Accessibility

Best Practices

SEO

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

fangdr.com

index.css

tab.css

toTop.1.0.css

fcqz.css

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

fangdr.com

index.css

tab.css

toTop.1.0.css

fcqz.css

jquery-1.8.0.min.js

ext-core.js

toTop.1.0.js

scxx.js

sinaflash.js

crapLoader.js

ajaxNewLoaderAds.js

index_index_duilian.js

index_index_windswf.js

index_index_top_hg.js

index_index_top_tl1.js

index_index_top_tll1.js

index_index_top_tll2.js

index_index_top_tll3.js

index_index_top_tll4.js

house.js

index_index_adstl1.js

index_index_top_tl2.js

index_index_adstl3.js

index_index_adstl4.js

index_index_adstl5.js

index_index_adstl6.js

index_index_adstl7.js

index_index_adstl8.js

jquery.KinSlideshow-1.2.1.min.js

index_index_middle_right.js

index_index_middle_tl1.js

index_index_middle_tl2.js

index_index_middle_tl3.js

index_index_middle_tl4.js

index_index_bottom_right.js

index_index_three_tl.js

index_index_three_tl2.js

index_index_three_tl3.js

index_index_three_tl4.js

index_top_web_push.js

adbox-v1.js

FC-replay120-200.js

javascript;base64,Y3JhcExvYWRlci5fb2x0PTI=