Report Summary

  • 53

    Performance

    Renders faster than
    70% of other websites

  • 64

    Accessibility

    Visual factors better than
    that of 29% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

crazyphper.com

一个泡面 · konakona的历史已经展开

Page Load Speed

20.5 sec in total

First Response

1.1 sec

Resources Loaded

18.8 sec

Page Rendered

588 ms

crazyphper.com screenshot

About Website

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

KONAKONA的个人网站。一个Freelancer,爱好旅行、摄影、产品和创造。25岁之前长期征战在代码的世界里,25岁后决心走上泡面的不归路。然而最渴望的确是精神自由。

Visit crazyphper.com

Key Findings

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

Performance Metrics

crazyphper.com performance score

53

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.0 s

9/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

9/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value110 ms

97/100

30%

CLS (Cumulative Layout Shift)

Value0.048

99/100

15%

TTI (Time to Interactive)

Value7.1 s

52/100

10%

Network Requests Diagram

crazyphper.com

1112 ms

global.min.css

805 ms

responsive.min.css

503 ms

jquery-jvectormap-1.2.2.css

350 ms

css

2091 ms

Our browser made a total of 36 requests to load all elements on the main page. We found that 22% of them (8 requests) were addressed to the original Crazyphper.com, 53% (19 requests) were made to Crazyphper-com.b0.upaiyun.com and 6% (2 requests) were made to Cdn.clicktale.net. The less responsive or slowest element that took the longest time to load (16 sec) relates to the external source Tajs.qq.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 447.4 kB (11%)

Content Size

4.1 MB

After Optimization

3.7 MB

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

HTML Optimization

-78%

Potential reduce by 44.7 kB

  • Original 57.0 kB
  • After minification 48.7 kB
  • After compression 12.4 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.3 kB, which is 15% 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 44.7 kB or 78% of the original size.

Image Optimization

-3%

Potential reduce by 111.8 kB

  • Original 3.7 MB
  • After minification 3.6 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. Crazyphper images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 121.3 kB

  • Original 201.3 kB
  • After minification 200.9 kB
  • After compression 79.9 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 121.3 kB or 60% of the original size.

CSS Optimization

-87%

Potential reduce by 169.6 kB

  • Original 194.9 kB
  • After minification 179.5 kB
  • After compression 25.2 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. Crazyphper.com needs all CSS files to be minified and compressed as it can save up to 169.6 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (31%)

Requests Now

32

After Optimization

22

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

Accessibility Review

crazyphper.com accessibility score

64

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

High

Links do not have a discernible name

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

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

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

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

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