Tools & Wizards About Us
404-notfound.net screenshot

Report Summary

  • 54

    Performance

    Renders faster than
    71% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

404-notfound.net

尕鈺小說-書友最值得收藏的網絡小說繁體小說網

Page Load Speed

3.1 sec in total

First Response

227 ms

Resources Loaded

2.6 sec

Page Rendered

317 ms

404-notfound.net screenshot

About Website

Visit 404-notfound.net now to see the best up-to-date 404 Notfound content and also check out these interesting facts you probably never knew about 404-notfound.net

免費繁體小說,更多好看的小說繁體小說儘在尕鈺小說，思路客為您提供最新熱門好看的火爆小說全文在線免費繁體小說、經典完結虐心的網絡小說小說排行榜及網絡小說免費下載。

Visit 404-notfound.net

Key Findings

We analyzed 404-notfound.net page load time and found that the first response time was 227 ms and then it took 2.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

404-notfound.net performance score

54

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.9 s

24/100

10%

LCP (Largest Contentful Paint)

Value4.6 s

36/100

25%

SI (Speed Index)

Value4.5 s

73/100

10%

TBT (Total Blocking Time)

Value450 ms

63/100

30%

CLS (Cumulative Layout Shift)

Value0.245

51/100

15%

TTI (Time to Interactive)

Value4.3 s

84/100

10%

Network Requests Diagram

227 ms

ga.js

19 ms

wp-emoji-release.min.js

206 ms

wp-syntax.css

334 ms

style.css

524 ms

Our browser made a total of 32 requests to load all elements on the main page. We found that 53% of them (17 requests) were addressed to the original 404-notfound.net, 6% (2 requests) were made to Google-analytics.com and 6% (2 requests) were made to Staticxx.facebook.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source I2.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 392.2 kB (74%)

Content Size

531.9 kB

After Optimization

139.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 404-notfound.net main page is 531.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 40% of websites need less resources to load. Javascripts take 254.9 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 38.2 kB

  • Original 47.5 kB
  • After minification 45.0 kB
  • After compression 9.3 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 38.2 kB or 80% of the original size.

Image Optimization

-7%

Potential reduce by 396 B

  • Original 5.8 kB
  • After minification 5.4 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. 404 Notfound images are well optimized though.

JavaScript Optimization

-65%

Potential reduce by 165.5 kB

  • Original 254.9 kB
  • After minification 230.5 kB
  • After compression 89.3 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 165.5 kB or 65% of the original size.

CSS Optimization

-84%

Potential reduce by 188.0 kB

  • Original 223.7 kB
  • After minification 188.5 kB
  • After compression 35.7 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. 404-notfound.net needs all CSS files to be minified and compressed as it can save up to 188.0 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (67%)

Requests Now

30

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

227 ms

ga.js

ga.js

19 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

206 ms

wp-syntax.css

wp-syntax.css

334 ms

style.css

style.css

524 ms

css

css

40 ms

font-awesome.css

font-awesome.css

403 ms

style.css

style.css

389 ms

jetpack.css

jetpack.css

420 ms

jquery.js

jquery.js

753 ms

jquery-migrate.min.js

jquery-migrate.min.js

588 ms

loader.js

loader.js

136 ms

twocolumns.css

twocolumns.css

652 ms

platform.js

platform.js

67 ms

jquery.cycle.js

jquery.cycle.js

933 ms

slideshow-shortcode.js

slideshow-shortcode.js

823 ms

devicepx-jetpack.js

devicepx-jetpack.js

31 ms

masonry.min.js

masonry.min.js

871 ms

bootstrap.js

bootstrap.js

822 ms

theme.js

theme.js

871 ms

e-201611.js

e-201611.js

30 ms

__utm.gif

__utm.gif

13 ms

sdk.js

sdk.js

74 ms

144107b38e4aa03d8f24d6b2776f67d1

144107b38e4aa03d8f24d6b2776f67d1

61 ms

nginx_cache_hit_rate-day.png

nginx_cache_hit_rate-day.png

1090 ms

orange-large.png

orange-large.png

217 ms

widgets.js

widgets.js

11 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

631 ms

49 ms

xd_arbiter.php

xd_arbiter.php

65 ms

xd_arbiter.php

xd_arbiter.php

120 ms

g.gif

g.gif

3 ms

Accessibility Review

404-notfound.net accessibility score

89

Accessibility Issues

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.

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

Best Practices

404-notfound.net 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

SEO Factors

404-notfound.net SEO score

85

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

    JA

  • Encoding

    UTF-8

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

404-notfound.net

Open Graph data is detected on the main page of 404 Notfound. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: