Tools & Wizards About Us
linglingfa.com screenshot

Report Summary

  • 40

    Performance

    Renders faster than
    59% of other websites

  • 67

    Accessibility

    Visual factors better than
    that of 32% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

linglingfa.com

零零发Blog

Page Load Speed

17.4 sec in total

First Response

30 ms

Resources Loaded

16.9 sec

Page Rendered

414 ms

linglingfa.com screenshot

About Website

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

see the world

Visit linglingfa.com

Key Findings

We analyzed Linglingfa.com page load time and found that the first response time was 30 ms and then it took 17.3 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

linglingfa.com performance score

40

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

16/100

10%

LCP (Largest Contentful Paint)

Value5.9 s

14/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value520 ms

56/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value10.7 s

22/100

10%

Network Requests Diagram

linglingfa.com

30 ms

linglingfa.com

59 ms

main.css

246 ms

font-awesome.css

384 ms

style.min.css

43 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 3% of them (2 requests) were addressed to the original Linglingfa.com, 50% (34 requests) were made to Cdn.jsdelivr.net and 6% (4 requests) were made to Unpkg.com. The less responsive or slowest element that took the longest time to load (13.5 sec) relates to the external source Fonts.geekzu.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.2 MB (31%)

Content Size

3.9 MB

After Optimization

2.7 MB

  • HTML
  • Images

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

HTML Optimization

-84%

Potential reduce by 676.8 kB

  • Original 808.4 kB
  • After minification 799.6 kB
  • After compression 131.6 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 676.8 kB or 84% of the original size.

Image Optimization

-17%

Potential reduce by 524.0 kB

  • Original 3.1 MB
  • After minification 2.5 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, Linglingfa needs image optimization as it can save up to 524.0 kB or 17% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

Number of requests can be reduced by 37 (61%)

Requests Now

61

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

linglingfa.com

linglingfa.com

30 ms

linglingfa.com

linglingfa.com

59 ms

main.css

main.css

246 ms

font-awesome.css

font-awesome.css

384 ms

style.min.css

style.min.css

43 ms

style.min.css

style.min.css

44 ms

css

css

13525 ms

style.min.css

style.min.css

50 ms

style.min.css

style.min.css

50 ms

style.min.css

style.min.css

217 ms

mediacloud-mux.blocks.style.min.css

mediacloud-mux.blocks.style.min.css

132 ms

emojify.min.css

emojify.min.css

53 ms

jquery.min.js

jquery.min.js

53 ms

jquery-migrate.min.js

jquery-migrate.min.js

53 ms

icons-2.6.4.js

icons-2.6.4.js

136 ms

jquery.min.js

jquery.min.js

287 ms

js

js

88 ms

waline.css

waline.css

332 ms

lazyload.css

lazyload.css

231 ms

main.js

main.js

325 ms

clipboard.min.js

clipboard.min.js

138 ms

emojify.min.js

emojify.min.js

140 ms

wp-embed.js

wp-embed.js

319 ms

lazySizesConfig.js

lazySizesConfig.js

393 ms

ls.unveilhooks.min.js

ls.unveilhooks.min.js

231 ms

ls.bgset.min.js

ls.bgset.min.js

233 ms

lazysizes.min.js

lazysizes.min.js

235 ms

image.js

image.js

413 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

121 ms

waline.css

waline.css

19 ms

223.gif

223.gif

1684 ms

image.png

image.png

1247 ms

1683256029370.jpg

1683256029370.jpg

1245 ms

remeber.forget.jpeg

remeber.forget.jpeg

1299 ms

yinheyingxiong.jpg

yinheyingxiong.jpg

1542 ms

bbs_2.png

bbs_2.png

1241 ms

w700d1q75cms.jpg

w700d1q75cms.jpg

1385 ms

MTMxMDI2NjExNzQwNDcxNTM_373059_HpN_3wI94Ab72Uga_1715766409

MTMxMDI2NjExNzQwNDcxNTM_373059_HpN_3wI94Ab72Uga_1715766409

3277 ms

26e34076cb9b4d7cb52bd17b71859e18.jpeg

26e34076cb9b4d7cb52bd17b71859e18.jpeg

1238 ms

104.jpg

104.jpg

1609 ms

v2-648dd9fa2696eef90d774230a67fe20c_720w.webp

v2-648dd9fa2696eef90d774230a67fe20c_720w.webp

1548 ms

how-to-get-accurate-translations-from-ai-translation-softwares-1536x864.png

how-to-get-accurate-translations-from-ai-translation-softwares-1536x864.png

2302 ms

https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F083b01d7-6fe7-4c90-b22e-6b008e9f15be_1262x760.png

https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F083b01d7-6fe7-4c90-b22e-6b008e9f15be_1262x760.png

205 ms

55054564-packs-dollars-background-lots-of-cash-money.jpg

55054564-packs-dollars-background-lots-of-cash-money.jpg

246 ms

56d48c41e9b3e393f3e7f416ed0948a3.png

56d48c41e9b3e393f3e7f416ed0948a3.png

251 ms

def0db1bda491dcbbb43d0a086416bb6.png

def0db1bda491dcbbb43d0a086416bb6.png

1404 ms

newtonandappletree3.jpg

newtonandappletree3.jpg

1302 ms

image.png

image.png

1345 ms

image.png

image.png

254 ms

w700d1q75cms.jpg

w700d1q75cms.jpg

1444 ms

1f5b0b4012c55d81a369fd94ff38390e.png

1f5b0b4012c55d81a369fd94ff38390e.png

239 ms

css-vars-ponyfill@2.3.2

css-vars-ponyfill@2.3.2

85 ms

main.css

main.css

30 ms

font-awesome.css

font-awesome.css

27 ms

style.min.css

style.min.css

36 ms

style.min.css

style.min.css

29 ms

css

css

71 ms

style.min.css

style.min.css

27 ms

style.min.css

style.min.css

28 ms

style.min.css

style.min.css

39 ms

mediacloud-mux.blocks.style.min.css

mediacloud-mux.blocks.style.min.css

38 ms

emojify.min.css

emojify.min.css

40 ms

waline.css

waline.css

36 ms

lazyload.css

lazyload.css

38 ms

waline.css

waline.css

28 ms

1f5b0b4012c55d81a369fd94ff38390e.png

1f5b0b4012c55d81a369fd94ff38390e.png

1001 ms

56d48c41e9b3e393f3e7f416ed0948a3.png

56d48c41e9b3e393f3e7f416ed0948a3.png

1001 ms

loading.gif

loading.gif

212 ms

Accessibility Review

linglingfa.com accessibility score

67

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.

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

linglingfa.com best practices score

67

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

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

    ZH

  • Language Claimed

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Linglingfa.com can be misinterpreted by Google and other search engines. Our service has detected that Chinese is used on the page, and it matches the claimed language. Our system also found out that Linglingfa.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

linglingfa.com

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