Tools & Wizards About Us
ui.live screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

ui.live

UI Design Resources, UI Kits, Wireframes, Icons and More - UI8

Page Load Speed

605 ms in total

First Response

34 ms

Resources Loaded

515 ms

Page Rendered

56 ms

ui.live screenshot

About Website

Welcome to ui.live homepage info - get ready to check UI best content right away, or after learning these important things about ui.live

100% curated digital marketplace with a growing library of high quality UX/UI design resources and freebies for designers.

Visit ui.live

Key Findings

We analyzed Ui.live page load time and found that the first response time was 34 ms and then it took 571 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

ui.live performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.8 s

0/100

10%

LCP (Largest Contentful Paint)

Value11.6 s

0/100

25%

SI (Speed Index)

Value8.5 s

18/100

10%

TBT (Total Blocking Time)

Value2,060 ms

7/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value19.4 s

2/100

10%

Network Requests Diagram

ui.live

34 ms

ui8.net

41 ms

ui8.net

100 ms

script.js

61 ms

app.min.5010a07.css

52 ms

Our browser made a total of 31 requests to load all elements on the main page. We found that 3% of them (1 request) were addressed to the original Ui.live, 58% (18 requests) were made to Ui8.net and 10% (3 requests) were made to Js.stripe.com. The less responsive or slowest element that took the longest time to load (207 ms) relates to the external source Static.cloudflareinsights.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 55.5 kB (42%)

Content Size

132.3 kB

After Optimization

76.7 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ui.live main page is 132.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. 50% of websites need less resources to load. HTML takes 79.8 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 55.5 kB

  • Original 79.8 kB
  • After minification 79.7 kB
  • After compression 24.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 55.5 kB or 70% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 10.5 kB
  • After minification 10.5 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. UI images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 67 B

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

Requests Breakdown

Number of requests can be reduced by 11 (44%)

Requests Now

25

After Optimization

14

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ui.live

ui.live

34 ms

ui8.net

ui8.net

41 ms

ui8.net

ui8.net

100 ms

script.js

script.js

61 ms

app.min.5010a07.css

app.min.5010a07.css

52 ms

js

js

205 ms

bugsnag.min.js

bugsnag.min.js

53 ms

vendor.min.5e167c1.js

vendor.min.5e167c1.js

107 ms

50 ms

tapfiliate.js

tapfiliate.js

52 ms

email-decode.min.js

email-decode.min.js

30 ms

app_spa.min.34ef2c5.js

app_spa.min.34ef2c5.js

183 ms

api.js

api.js

181 ms

0376.js

0376.js

181 ms

email.min.js

email.min.js

45 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

207 ms

sapiens.jpg

sapiens.jpg

53 ms

peeps.jpg

peeps.jpg

52 ms

figma-prog.svg

figma-prog.svg

46 ms

framer-prog.svg

framer-prog.svg

45 ms

react-prog.svg

react-prog.svg

92 ms

blender-prog.svg

blender-prog.svg

94 ms

c4d-prog.svg

c4d-prog.svg

82 ms

ps-prog.svg

ps-prog.svg

95 ms

ai-prog.svg

ai-prog.svg

93 ms

CircularXX-Book.woff

CircularXX-Book.woff

76 ms

CircularXX-Regular.woff

CircularXX-Regular.woff

119 ms

CircularXX-Medium.woff

CircularXX-Medium.woff

120 ms

channel.html

channel.html

9 ms

outer.html

outer.html

4 ms

inner.html

inner.html

17 ms

Accessibility Review

ui.live accessibility score

79

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

Buttons do not have an accessible name

High

Links do not have a discernible name

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

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

ui.live best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

ui.live SEO score

89

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ui.live can be misinterpreted by Google and other search engines. Our service has detected that English 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 Ui.live 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

ui.live

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