Tools & Wizards About Us
uigreat.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

uigreat.com

优阁(UIGREAT) - UI设计师学习交流社区

Page Load Speed

3.6 sec in total

First Response

572 ms

Resources Loaded

3 sec

Page Rendered

75 ms

uigreat.com screenshot

About Website

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

UIGREAT-优阁,是一个UI设计师学习交流分享的平台，免费的UI设计公开课成功引导UI新人设计师入门，分享最新UI设计教程，UI设计资源给大家提供更多的学习与工作机会

Visit uigreat.com

Key Findings

We analyzed Uigreat.com page load time and found that the first response time was 572 ms and then it took 3 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

uigreat.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.6 s

0/100

10%

LCP (Largest Contentful Paint)

Value14.7 s

0/100

25%

SI (Speed Index)

Value18.0 s

0/100

10%

TBT (Total Blocking Time)

Value940 ms

30/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value15.3 s

7/100

10%

Network Requests Diagram

uigreat.com

572 ms

aliplayer-min.css

37 ms

aliplayer-min.js

46 ms

jweixin-1.6.0.js

209 ms

2.6057f008.chunk.css

737 ms

Our browser made a total of 10 requests to load all elements on the main page. We found that 50% of them (5 requests) were addressed to the original Uigreat.com, 20% (2 requests) were made to G.alicdn.com and 20% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Uigreat.com.

Page Optimization Overview & Recommendations

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

Content Size

95.3 kB

After Optimization

85.0 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Uigreat.com main page is 95.3 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. 25% of websites need less resources to load. Javascripts take 87.6 kB which makes up the majority of the site volume.

HTML Optimization

-50%

Potential reduce by 1.7 kB

  • Original 3.3 kB
  • After minification 3.3 kB
  • After compression 1.6 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 1.7 kB or 50% of the original size.

JavaScript Optimization

-10%

Potential reduce by 8.6 kB

  • Original 87.6 kB
  • After minification 87.6 kB
  • After compression 79.0 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 10 B

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

Requests Breakdown

Number of requests can be reduced by 7 (78%)

Requests Now

9

After Optimization

2

  • JavaScript
  • CSS

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

Network Requests Diagram

uigreat.com

uigreat.com

572 ms

aliplayer-min.css

aliplayer-min.css

37 ms

aliplayer-min.js

aliplayer-min.js

46 ms

jweixin-1.6.0.js

jweixin-1.6.0.js

209 ms

2.6057f008.chunk.css

2.6057f008.chunk.css

737 ms

main.8e7ae5ea.chunk.css

main.8e7ae5ea.chunk.css

729 ms

2.e1520de0.chunk.js

2.e1520de0.chunk.js

2243 ms

main.d10d025f.chunk.js

main.d10d025f.chunk.js

1247 ms

css

css

49 ms

css

css

67 ms

Accessibility Review

uigreat.com accessibility score

71

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.

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

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

uigreat.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

SEO Factors

uigreat.com SEO score

90

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

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

    ZH

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Uigreat.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 Uigreat.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

uigreat.com

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