Tools & Wizards About Us
nanoyun.com screenshot

Report Summary

  • 72

    Performance

    Renders faster than
    82% of other websites

  • 43

    Accessibility

    Visual factors better than
    that of 19% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

nanoyun.com

牛小秘 - 身边的贴身小助手，最新学习资源

Page Load Speed

23.2 sec in total

First Response

1 sec

Resources Loaded

21.7 sec

Page Rendered

406 ms

nanoyun.com screenshot

About Website

Visit nanoyun.com now to see the best up-to-date Nanoyun content for China and also check out these interesting facts you probably never knew about nanoyun.com

牛小秘之贴身小秘提供各类最新的参考资料供广大用户学习交流。如最新热门电影观后感，最新畅销书籍读后感，大型学习教育活动心得体会，最新中高考满分作文、学习方法等等！

Visit nanoyun.com

Key Findings

We analyzed Nanoyun.com page load time and found that the first response time was 1 sec and then it took 22.1 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

nanoyun.com performance score

72

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

37/100

10%

LCP (Largest Contentful Paint)

Value3.9 s

52/100

25%

SI (Speed Index)

Value6.1 s

44/100

10%

TBT (Total Blocking Time)

Value200 ms

90/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.3 s

85/100

10%

Network Requests Diagram

nanoyun.com

1021 ms

iconfont.css

478 ms

stui_block.css

501 ms

stui_block_color.css

545 ms

stui_default.css

554 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 78% of them (39 requests) were addressed to the original Nanoyun.com, 12% (6 requests) were made to Hm.baidu.com and 2% (1 request) were made to Sdk.51.la. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Youku.youkuphoto.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 267.3 kB (24%)

Content Size

1.1 MB

After Optimization

852.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Nanoyun.com main page is 1.1 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. 50% of websites need less resources to load. Images take 732.7 kB which makes up the majority of the site volume.

HTML Optimization

-93%

Potential reduce by 218.6 kB

  • Original 236.1 kB
  • After minification 199.3 kB
  • After compression 17.5 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 36.8 kB, which is 16% 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 218.6 kB or 93% of the original size.

Image Optimization

-2%

Potential reduce by 17.7 kB

  • Original 732.7 kB
  • After minification 715.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. Nanoyun images are well optimized though.

JavaScript Optimization

-21%

Potential reduce by 26.4 kB

  • Original 123.1 kB
  • After minification 122.1 kB
  • After compression 96.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 26.4 kB or 21% of the original size.

CSS Optimization

-17%

Potential reduce by 4.6 kB

  • Original 27.5 kB
  • After minification 27.5 kB
  • After compression 22.9 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. Nanoyun.com needs all CSS files to be minified and compressed as it can save up to 4.6 kB or 17% of the original size.

Requests Breakdown

Number of requests can be reduced by 16 (36%)

Requests Now

45

After Optimization

29

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

nanoyun.com

nanoyun.com

1021 ms

iconfont.css

iconfont.css

478 ms

stui_block.css

stui_block.css

501 ms

stui_block_color.css

stui_block_color.css

545 ms

stui_default.css

stui_default.css

554 ms

jquery.min.js

jquery.min.js

952 ms

stui_default.js

stui_default.js

1016 ms

stui_block.js

stui_block.js

749 ms

common.js

common.js

749 ms

function.js

function.js

815 ms

play.js

play.js

830 ms

history.js

history.js

1039 ms

tj.js

tj.js

999 ms

autocomplete.js

autocomplete.js

1086 ms

js-sdk-pro.min.js

js-sdk-pro.min.js

280 ms

hm.js

hm.js

962 ms

hm.js

hm.js

1185 ms

logo_f.png

logo_f.png

427 ms

icon_2.png

icon_2.png

259 ms

icon_12.png

icon_12.png

292 ms

icon_25.png

icon_25.png

292 ms

icon_26.png

icon_26.png

251 ms

gLtqripAA==

gLtqripAA==

0 ms

load.gif

load.gif

273 ms

play.png

play.png

411 ms

push.js

push.js

755 ms

hm.js

hm.js

952 ms

share.js

share.js

316 ms

e18e861a29222fbb4e20bded3fc32972.jpg

e18e861a29222fbb4e20bded3fc32972.jpg

19651 ms

653610e6633d7.jpg

653610e6633d7.jpg

983 ms

65387e20e957d.jpg

65387e20e957d.jpg

573 ms

655eaf182eac0.jpg

655eaf182eac0.jpg

622 ms

655ef824786ee.jpg

655ef824786ee.jpg

903 ms

65388b6d9532a.jpg

65388b6d9532a.jpg

743 ms

656543be7b1d9.jpg

656543be7b1d9.jpg

1008 ms

652c92d3991f2.jpg

652c92d3991f2.jpg

859 ms

65336358db98f.jpg

65336358db98f.jpg

903 ms

652cac6b305a8.jpg

652cac6b305a8.jpg

992 ms

654b5f9d2d420.jpg

654b5f9d2d420.jpg

1144 ms

654b5f8dc3f45.jpg

654b5f8dc3f45.jpg

1164 ms

654b6e4665095.jpg

654b6e4665095.jpg

1166 ms

654b6e4623198.jpg

654b6e4623198.jpg

1259 ms

654b6e45d3d70.jpg

654b6e45d3d70.jpg

1241 ms

654b6e43c7c42.jpg

654b6e43c7c42.jpg

1266 ms

654b6e43849e1.jpg

654b6e43849e1.jpg

1429 ms

654b6e4299b1f.jpg

654b6e4299b1f.jpg

1435 ms

collect

collect

502 ms

hm.gif

hm.gif

300 ms

hm.gif

hm.gif

313 ms

hm.gif

hm.gif

322 ms

Accessibility Review

nanoyun.com accessibility score

43

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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible 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.

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

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

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

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

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

nanoyun.com best practices score

58

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

nanoyun.com SEO score

83

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

High

Tap targets are not sized appropriately

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

nanoyun.com

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