Tools & Wizards About Us
getnas.com screenshot

Report Summary

  • 86

    Performance

    Renders faster than
    89% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 75% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

getnas.com

GetNAS 网站已正式下线 | 开源周末

Page Load Speed

45.2 sec in total

First Response

2.6 sec

Resources Loaded

42.3 sec

Page Rendered

386 ms

getnas.com screenshot

About Website

Welcome to getnas.com homepage info - get ready to check GetNAS best content for China right away, or after learning these important things about getnas.com

GetNAS中文网，为您提供FreeNAS中文版安装使用教程以及最新版本分流下载，为 DIY NAS 的网友提供丰富的硬件指南和组装方案，帮助构建适用于中小企业和家庭环境的NAS存储服务器。

Visit getnas.com

Key Findings

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

getnas.com performance score

86

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

69/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value3.3 s

91/100

10%

TBT (Total Blocking Time)

Value230 ms

86/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value5.6 s

69/100

10%

Network Requests Diagram

getnas.com

2568 ms

www.getnas.com

4840 ms

uikit.css

10544 ms

style.css

3416 ms

jquery.min.js

6780 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 48% of them (35 requests) were addressed to the original Getnas.com, 36% (26 requests) were made to 7xnt0e.com1.z0.glb.clouddn.com and 4% (3 requests) were made to Static.duoshuo.com. The less responsive or slowest element that took the longest time to load (19.9 sec) belongs to the original domain Getnas.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 439.4 kB (31%)

Content Size

1.4 MB

After Optimization

963.1 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Getnas.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. 45% of websites need less resources to load. Images take 901.6 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 63.6 kB

  • Original 72.8 kB
  • After minification 41.3 kB
  • After compression 9.2 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 31.4 kB, which is 43% 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 63.6 kB or 87% of the original size.

Image Optimization

-7%

Potential reduce by 66.7 kB

  • Original 901.6 kB
  • After minification 835.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. GetNAS images are well optimized though.

JavaScript Optimization

-62%

Potential reduce by 141.3 kB

  • Original 226.9 kB
  • After minification 225.2 kB
  • After compression 85.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 141.3 kB or 62% of the original size.

CSS Optimization

-83%

Potential reduce by 167.8 kB

  • Original 201.1 kB
  • After minification 174.7 kB
  • After compression 33.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. Getnas.com needs all CSS files to be minified and compressed as it can save up to 167.8 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 17 (24%)

Requests Now

70

After Optimization

53

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

getnas.com

getnas.com

2568 ms

www.getnas.com

www.getnas.com

4840 ms

uikit.css

uikit.css

10544 ms

style.css

style.css

3416 ms

jquery.min.js

jquery.min.js

6780 ms

uikit.min.js

uikit.min.js

3993 ms

tooltip.min.js

tooltip.min.js

3723 ms

widget.css

widget.css

3688 ms

wpfront-scroll-top.css

wpfront-scroll-top.css

5425 ms

pagenavi-css.css

pagenavi-css.css

4073 ms

jquery.js

jquery.js

16041 ms

jquery-migrate.min.js

jquery-migrate.min.js

6001 ms

wpfront-scroll-top.js

wpfront-scroll-top.js

4458 ms

m.js

m.js

875 ms

embed.js

embed.js

522 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

2479 ms

hm.js

hm.js

839 ms

group.png

group.png

2147 ms

20150602104239.png

20150602104239.png

7230 ms

logo.png

logo.png

361 ms

freenas-feture.png

freenas-feture.png

19898 ms

bacula.jpg

bacula.jpg

2062 ms

owncloud.jpg

owncloud.jpg

3962 ms

btsync.jpg

btsync.jpg

2625 ms

transmission.jpg

transmission.jpg

2188 ms

Syncthing.jpg

Syncthing.jpg

1957 ms

crashplan.jpg

crashplan.jpg

2788 ms

plex.jpg

plex.jpg

3221 ms

subsonic.jpg

subsonic.jpg

4825 ms

emby.jpg

emby.jpg

5756 ms

sickbeard.jpg

sickbeard.jpg

3615 ms

CrucibleWDS.jpg

CrucibleWDS.jpg

3988 ms

CouchPotato.jpg

CouchPotato.jpg

4447 ms

freenas-logo.png

freenas-logo.png

5475 ms

wordpress-logo.png

wordpress-logo.png

5782 ms

github-logo.png

github-logo.png

4860 ms

uikit-logo.jpg

uikit-logo.jpg

7830 ms

phpwind-logo.png

phpwind-logo.png

5273 ms

39.png

39.png

5687 ms

%E7%81%AB%E7%8B%90%E6%88%AA%E5%9B%BE_2015-05-12T04-44-50.646Z.png

%E7%81%AB%E7%8B%90%E6%88%AA%E5%9B%BE_2015-05-12T04-44-50.646Z.png

9558 ms

%E7%81%AB%E7%8B%90%E6%88%AA%E5%9B%BE_2015-05-12T04-25-36.714Z.png

%E7%81%AB%E7%8B%90%E6%88%AA%E5%9B%BE_2015-05-12T04-25-36.714Z.png

12845 ms

20150428182455.png

20150428182455.png

7746 ms

20150602154021.png

20150602154021.png

6107 ms

2015-05-12T06-44-28.636Z.png

2015-05-12T06-44-28.636Z.png

16780 ms

2015-05-12T06-04-17.482Z.png

2015-05-12T06-04-17.482Z.png

12719 ms

2015-05-12T05-33-29.623Z.png

2015-05-12T05-33-29.623Z.png

15007 ms

20150602132620.png

20150602132620.png

9129 ms

20150602130136.png

20150602130136.png

9593 ms

20150602125615.png

20150602125615.png

11765 ms

20150602115237.png

20150602115237.png

10062 ms

20150603142959.png

20150603142959.png

10983 ms

20150603141309.png

20150603141309.png

12366 ms

20150603140038.png

20150603140038.png

13046 ms

2015-05-12T06-29-16.919Z.png

2015-05-12T06-29-16.919Z.png

16556 ms

20150603170826.png

20150603170826.png

15554 ms

20150603164404.png

20150603164404.png

14202 ms

20150603163118.png

20150603163118.png

13873 ms

20150603120930.png

20150603120930.png

14704 ms

20150603113056.png

20150603113056.png

15584 ms

20150603112458.png

20150603112458.png

16391 ms

20150603110850.png

20150603110850.png

16686 ms

3_350x350.jpg

3_350x350.jpg

18397 ms

20150603132046.png

20150603132046.png

16045 ms

TB2wdMncpXXXXcoXpXXXXXXXXXX_683588240.jpg

TB2wdMncpXXXXcoXpXXXXXXXXXX_683588240.jpg

16991 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

16840 ms

icon.gif

icon.gif

6371 ms

embed.bluebox.css

embed.bluebox.css

174 ms

embed.compat.js

embed.compat.js

515 ms

hm.gif

hm.gif

415 ms

o.htm

o.htm

708 ms

hm.gif

hm.gif

1646 ms

wh.js

wh.js

864 ms

ac.js

ac.js

662 ms

Accessibility Review

getnas.com accessibility score

90

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

Image elements do not have [alt] attributes

Best Practices

getnas.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

getnas.com SEO score

58

Search Engine Optimization Advices

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

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

getnas.com

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