Tools & Wizards About Us
fudanky.com screenshot

Report Summary

  • 0

    Performance

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

Page Load Speed

4.7 sec in total

First Response

299 ms

Resources Loaded

4 sec

Page Rendered

377 ms

fudanky.com screenshot

About Website

Click here to check amazing Fudanky content. Otherwise, check out these important facts you probably never knew about fudanky.com

Visit fudanky.com

Key Findings

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

Performance Metrics

fudanky.com performance score

0

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

54/100

10%

LCP (Largest Contentful Paint)

Value0

0/100

25%

SI (Speed Index)

Value5.0 s

63/100

10%

TBT (Total Blocking Time)

Value410 ms

67/100

30%

CLS (Cumulative Layout Shift)

Value0.449

20/100

15%

TTI (Time to Interactive)

Value6.8 s

56/100

10%

Network Requests Diagram

index.php

299 ms

bootstrap.css

198 ms

bootstrap-theme.css

138 ms

base.css

141 ms

index.css

148 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 90% of them (43 requests) were addressed to the original Fudanky.com, 8% (4 requests) were made to Hm.baidu.com and 2% (1 request) were made to Push.zhanzhang.baidu.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Push.zhanzhang.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 809.3 kB (37%)

Content Size

2.2 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-81%

Potential reduce by 25.0 kB

  • Original 30.8 kB
  • After minification 22.9 kB
  • After compression 5.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. This page needs HTML code to be minified as it can gain 8.0 kB, which is 26% 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 25.0 kB or 81% of the original size.

Image Optimization

-37%

Potential reduce by 780.2 kB

  • Original 2.1 MB
  • After minification 1.3 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. Obviously, Fudanky needs image optimization as it can save up to 780.2 kB or 37% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-46%

Potential reduce by 366 B

  • Original 799 B
  • After minification 731 B
  • After compression 433 B

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 366 B or 46% of the original size.

CSS Optimization

-11%

Potential reduce by 3.7 kB

  • Original 32.8 kB
  • After minification 32.8 kB
  • After compression 29.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. Fudanky.com needs all CSS files to be minified and compressed as it can save up to 3.7 kB or 11% of the original size.

Requests Breakdown

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

Requests Now

46

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

index.php

index.php

299 ms

bootstrap.css

bootstrap.css

198 ms

bootstrap-theme.css

bootstrap-theme.css

138 ms

base.css

base.css

141 ms

index.css

index.css

148 ms

media.css

media.css

158 ms

mystyle.css

mystyle.css

156 ms

tj.js

tj.js

207 ms

common.js

common.js

209 ms

hm.js

hm.js

1252 ms

hm.js

hm.js

1480 ms

topbg.jpg

topbg.jpg

78 ms

head-black.png

head-black.png

79 ms

logo.png

logo.png

134 ms

weixin.png

weixin.png

79 ms

2wei.jpg

2wei.jpg

79 ms

weibo.png

weibo.png

79 ms

search05.png

search05.png

135 ms

1436250411.jpg

1436250411.jpg

337 ms

1436520797.jpg

1436520797.jpg

333 ms

1436520820.jpg

1436520820.jpg

269 ms

1436250422.jpg

1436250422.jpg

338 ms

bg-black.png

bg-black.png

199 ms

button16.png

button16.png

200 ms

1632302974.png

1632302974.png

742 ms

1615012946.png

1615012946.png

539 ms

1597821135.jpg

1597821135.jpg

402 ms

slider-arrow.png

slider-arrow.png

893 ms

qb2.jpg

qb2.jpg

404 ms

more1.jpg

more1.jpg

403 ms

tu1.jpg

tu1.jpg

476 ms

1436522806.jpg

1436522806.jpg

475 ms

1438219575.jpg

1438219575.jpg

475 ms

1436516230.jpg

1436516230.jpg

544 ms

1436515881.jpg

1436515881.jpg

541 ms

1436514790.jpg

1436514790.jpg

543 ms

1436514433.jpg

1436514433.jpg

600 ms

1436511420.jpg

1436511420.jpg

612 ms

1436522817.jpg

1436522817.jpg

613 ms

link.jpg

link.jpg

614 ms

1436517129.jpg

1436517129.jpg

666 ms

1436516860.jpg

1436516860.jpg

673 ms

1436255348.jpg

1436255348.jpg

675 ms

f2wei.jpg

f2wei.jpg

675 ms

weixin.jpg

weixin.jpg

738 ms

push.js

push.js

1523 ms

hm.gif

hm.gif

308 ms

hm.gif

hm.gif

318 ms

Accessibility Review

fudanky.com accessibility score

54

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

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

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

fudanky.com SEO score

92

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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Fudanky.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 Fudanky.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

fudanky.com

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