Tools & Wizards About Us
uid.me screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 63

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

uid.me

uid - profile page builder

Page Load Speed

4 sec in total

First Response

481 ms

Resources Loaded

3.4 sec

Page Rendered

131 ms

uid.me screenshot

About Website

Click here to check amazing Uid content for Russia. Otherwise, check out these important facts you probably never knew about uid.me

uID.me is a personal profile builder that allows to create unique layout for each page, as well as import and view data from all social networks

Visit uid.me

Key Findings

We analyzed Uid.me page load time and found that the first response time was 481 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

uid.me performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.3 s

41/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

5/100

25%

SI (Speed Index)

Value10.6 s

7/100

10%

TBT (Total Blocking Time)

Value620 ms

48/100

30%

CLS (Cumulative Layout Shift)

Value0.016

100/100

15%

TTI (Time to Interactive)

Value13.5 s

11/100

10%

Network Requests Diagram

uid.me

481 ms

uid.me

819 ms

css

60 ms

css

72 ms

font-awesome.min.css

25 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 74% of them (39 requests) were addressed to the original Uid.me, 8% (4 requests) were made to Fonts.gstatic.com and 6% (3 requests) were made to Mc.yandex.ru. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Uid.me.

Page Optimization Overview & Recommendations

Page size can be reduced by 216.2 kB (13%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Uid.me main page is 1.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. 35% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 42.9 kB

  • Original 54.8 kB
  • After minification 52.2 kB
  • After compression 11.8 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 42.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 572 B

  • Original 1.4 MB
  • After minification 1.4 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. Uid images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 43.2 kB

  • Original 103.1 kB
  • After minification 103.1 kB
  • After compression 59.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 43.2 kB or 42% of the original size.

CSS Optimization

-85%

Potential reduce by 129.5 kB

  • Original 153.2 kB
  • After minification 136.3 kB
  • After compression 23.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. Uid.me needs all CSS files to be minified and compressed as it can save up to 129.5 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 28 (60%)

Requests Now

47

After Optimization

19

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

uid.me

uid.me

481 ms

uid.me

uid.me

819 ms

css

css

60 ms

css

css

72 ms

font-awesome.min.css

font-awesome.min.css

25 ms

_.css

_.css

163 ms

_languages.css

_languages.css

323 ms

font_svg.css

font_svg.css

479 ms

global.css

global.css

484 ms

login.css

login.css

495 ms

feedback.min.css

feedback.min.css

496 ms

jquery-1.10.2.min.js

jquery-1.10.2.min.js

647 ms

jquery.carousel2.min.js

jquery.carousel2.min.js

491 ms

device.js

device.js

632 ms

uidme.js

uidme.js

643 ms

sign_in.js

sign_in.js

641 ms

browser_detection.min.js

browser_detection.min.js

641 ms

feedback.js

feedback.js

672 ms

logo120.svg

logo120.svg

292 ms

uid-logo.svg

uid-logo.svg

301 ms

background.png

background.png

781 ms

en.png

en.png

303 ms

ru.png

ru.png

306 ms

ar.png

ar.png

308 ms

de.png

de.png

449 ms

es.png

es.png

458 ms

fr.png

fr.png

460 ms

pt.png

pt.png

464 ms

ro.png

ro.png

465 ms

679 ms

ga.js

ga.js

50 ms

watch.js

watch.js

462 ms

mixpanel-2.2.min.js

mixpanel-2.2.min.js

230 ms

K88pR3goAWT7BTt32Z01mz8E0i7KZn-EPnyo3HZu7kw.woff

K88pR3goAWT7BTt32Z01mz8E0i7KZn-EPnyo3HZu7kw.woff

67 ms

DXI1ORHCpsQm3Vp6mXoaTZ1r3JsPcQLi8jytr04NNhU.woff

DXI1ORHCpsQm3Vp6mXoaTZ1r3JsPcQLi8jytr04NNhU.woff

73 ms

MTP_ySUJH_bn48VBG8sNSp1r3JsPcQLi8jytr04NNhU.woff

MTP_ySUJH_bn48VBG8sNSp1r3JsPcQLi8jytr04NNhU.woff

85 ms

k3k702ZOKiLJc3WVjuplzJ1r3JsPcQLi8jytr04NNhU.woff

k3k702ZOKiLJc3WVjuplzJ1r3JsPcQLi8jytr04NNhU.woff

87 ms

__utm.gif

__utm.gif

23 ms

cloud_richard.jpg

cloud_richard.jpg

877 ms

posterOverlay.png

posterOverlay.png

405 ms

olivia_cameron.jpg

olivia_cameron.jpg

882 ms

pixelkhaos.jpg

pixelkhaos.jpg

727 ms

ruben_wetzels.jpg

ruben_wetzels.jpg

720 ms

marjana_borodan.png

marjana_borodan.png

1255 ms

alexmoloney.png

alexmoloney.png

880 ms

dikaya.png

dikaya.png

1353 ms

roman_iuvshin.png

roman_iuvshin.png

1363 ms

lukina.png

lukina.png

1192 ms

olga.jpg

olga.jpg

1195 ms

oleg.jpg

oleg.jpg

1199 ms

22 ms

advert.gif

advert.gif

91 ms

1

1

92 ms

Accessibility Review

uid.me accessibility score

63

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

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

uid.me 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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

uid.me SEO score

92

Search Engine Optimization Advices

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

uid.me

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