Tools & Wizards About Us
gitnavi.com screenshot

Report Summary

  • 9

    Performance

    Renders faster than
    23% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 69

    SEO

    Google-friendlier than
    28% of websites

gitnavi.com

UPTMR-信未来-一个忠于用户自定义的引导网站

Page Load Speed

24.5 sec in total

First Response

638 ms

Resources Loaded

23.7 sec

Page Rendered

75 ms

gitnavi.com screenshot

About Website

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

UPTMR-信未来-一个忠于用户自定义的引导网站

Visit gitnavi.com

Key Findings

We analyzed Gitnavi.com page load time and found that the first response time was 638 ms and then it took 23.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

gitnavi.com performance score

9

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

4/100

10%

LCP (Largest Contentful Paint)

Value26.3 s

0/100

25%

SI (Speed Index)

Value13.9 s

1/100

10%

TBT (Total Blocking Time)

Value1,190 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.569

12/100

15%

TTI (Time to Interactive)

Value25.6 s

0/100

10%

Network Requests Diagram

gitnavi.com

638 ms

www.uptmr.com

690 ms

www.uptmr.com

917 ms

jquery.min.js

1601 ms

8baa441.css

1612 ms

Our browser made a total of 22 requests to load all elements on the main page. We found that 5% of them (1 request) were addressed to the original Gitnavi.com, 82% (18 requests) were made to Cdn.uptmr.com and 9% (2 requests) were made to Uptmr.com. The less responsive or slowest element that took the longest time to load (19.9 sec) relates to the external source Hm.baidu.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.7 MB (64%)

Content Size

2.7 MB

After Optimization

948.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Gitnavi.com main page is 2.7 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. Javascripts take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-69%

Potential reduce by 13.2 kB

  • Original 19.3 kB
  • After minification 19.0 kB
  • After compression 6.0 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 13.2 kB or 69% of the original size.

Image Optimization

-28%

Potential reduce by 1.8 kB

  • Original 6.6 kB
  • After minification 4.8 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. Obviously, Gitnavi needs image optimization as it can save up to 1.8 kB or 28% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-66%

Potential reduce by 1.7 MB

  • Original 2.6 MB
  • After minification 2.6 MB
  • After compression 866.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 1.7 MB or 66% of the original size.

CSS Optimization

-0%

Potential reduce by 56 B

  • Original 70.6 kB
  • After minification 70.6 kB
  • After compression 70.5 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. Gitnavi.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (72%)

Requests Now

18

After Optimization

5

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

gitnavi.com

gitnavi.com

638 ms

www.uptmr.com

www.uptmr.com

690 ms

www.uptmr.com

www.uptmr.com

917 ms

jquery.min.js

jquery.min.js

1601 ms

8baa441.css

8baa441.css

1612 ms

fcc3014.css

fcc3014.css

1639 ms

bc733ef.css

bc733ef.css

1636 ms

6a14da3.css

6a14da3.css

1635 ms

93d9a38.css

93d9a38.css

1642 ms

210969c.js

210969c.js

1838 ms

438acd6.js

438acd6.js

1848 ms

7b1a13b.js

7b1a13b.js

1850 ms

d9d5005.js

d9d5005.js

1854 ms

c45c361.js

c45c361.js

1853 ms

8ea7f08.js

8ea7f08.js

1856 ms

9a4be2d.js

9a4be2d.js

2392 ms

6918943.js

6918943.js

3848 ms

0a8c56b.js

0a8c56b.js

2088 ms

hm.js

hm.js

19856 ms

logo-40x40.269a404.png

logo-40x40.269a404.png

419 ms

weixin.e957d86.png

weixin.e957d86.png

422 ms

email.13133fe.png

email.13133fe.png

422 ms

Accessibility Review

gitnavi.com accessibility score

88

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

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

Best Practices

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

High

Missing source maps for large first-party JavaScript

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

gitnavi.com SEO score

69

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

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

gitnavi.com

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