Tools & Wizards About Us
url.cr screenshot

Report Summary

  • 46

    Performance

    Renders faster than
    65% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

url.cr

Short URL generation URL shortening service

Page Load Speed

15 sec in total

First Response

1.2 sec

Resources Loaded

13.7 sec

Page Rendered

102 ms

url.cr screenshot

About Website

Visit url.cr now to see the best up-to-date URL content and also check out these interesting facts you probably never knew about url.cr

Changes a big URL into tiny URL. With link editing, detailed click statistics, QR Codes and Custom Domains.

Visit url.cr

Key Findings

We analyzed Url.cr page load time and found that the first response time was 1.2 sec and then it took 13.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

url.cr performance score

46

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value11.0 s

0/100

10%

LCP (Largest Contentful Paint)

Value15.7 s

0/100

25%

SI (Speed Index)

Value11.0 s

6/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.042

99/100

15%

TTI (Time to Interactive)

Value16.6 s

5/100

10%

Network Requests Diagram

url.cr

1168 ms

url.cr

3387 ms

jquery-1.8.2.js

4607 ms

jquery.cookie.js

754 ms

google_Montserrat.css

1208 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 89% of them (39 requests) were addressed to the original Url.cr, 11% (5 requests) were made to Image.flaticon.com. The less responsive or slowest element that took the longest time to load (6.9 sec) belongs to the original domain Url.cr.

Page Optimization Overview & Recommendations

Page size can be reduced by 827.9 kB (67%)

Content Size

1.2 MB

After Optimization

406.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Url.cr main page is 1.2 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. Javascripts take 714.4 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 12.6 kB

  • Original 16.5 kB
  • After minification 12.6 kB
  • After compression 3.9 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 3.9 kB, which is 24% 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 12.6 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 18.5 kB

  • Original 239.7 kB
  • After minification 221.2 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. URL images are well optimized though.

JavaScript Optimization

-80%

Potential reduce by 574.5 kB

  • Original 714.4 kB
  • After minification 473.7 kB
  • After compression 139.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 574.5 kB or 80% of the original size.

CSS Optimization

-84%

Potential reduce by 222.3 kB

  • Original 264.2 kB
  • After minification 240.2 kB
  • After compression 41.9 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. Url.cr needs all CSS files to be minified and compressed as it can save up to 222.3 kB or 84% of the original size.

Requests Breakdown

Number of requests can be reduced by 24 (71%)

Requests Now

34

After Optimization

10

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

url.cr

url.cr

1168 ms

url.cr

url.cr

3387 ms

jquery-1.8.2.js

jquery-1.8.2.js

4607 ms

jquery.cookie.js

jquery.cookie.js

754 ms

google_Montserrat.css

google_Montserrat.css

1208 ms

font-awesome.min.css

font-awesome.min.css

2060 ms

bootstrap.min.css

bootstrap.min.css

5347 ms

paper-kit.css

paper-kit.css

5974 ms

weui.css

weui.css

3184 ms

jquery.i18n.min.js

jquery.i18n.min.js

2061 ms

change_lang.js

change_lang.js

2497 ms

lang_chang_div.css

lang_chang_div.css

2834 ms

popper.min.js

popper.min.js

2963 ms

bootstrap.min.js

bootstrap.min.js

5098 ms

bootstrap-switch.js

bootstrap-switch.js

3472 ms

nouislider.min.js

nouislider.min.js

4006 ms

moment.min.js

moment.min.js

3982 ms

bootstrap-tagsinput.js

bootstrap-tagsinput.js

4429 ms

bootstrap-selectpicker.js

bootstrap-selectpicker.js

5515 ms

bootstrap-datetimepicker.js

bootstrap-datetimepicker.js

5581 ms

photoswipe.min.js

photoswipe.min.js

5459 ms

photoswipe-ui-default.min.js

photoswipe-ui-default.min.js

5887 ms

init-gallery.js

init-gallery.js

6116 ms

jasny-bootstrap.min.js

jasny-bootstrap.min.js

6252 ms

paper-kit.js

paper-kit.js

6339 ms

main.js

main.js

6664 ms

clipboard.min.js

clipboard.min.js

6527 ms

fingerprint2.js

fingerprint2.js

6893 ms

299786.svg

299786.svg

109 ms

299820.svg

299820.svg

88 ms

299753.svg

299753.svg

84 ms

299693.svg

299693.svg

83 ms

299815.svg

299815.svg

56 ms

urlcr_weblogo_white.png

urlcr_weblogo_white.png

791 ms

usa02.png

usa02.png

1022 ms

cn01.png

cn01.png

1131 ms

ita02.png

ita02.png

1308 ms

redspeed-lisa.png

redspeed-lisa.png

1998 ms

live_weixin_1.png

live_weixin_1.png

1611 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1535 ms

i18n_cn.json

i18n_cn.json

880 ms

getpostjson.ashx

getpostjson.ashx

1495 ms

fontawesome-webfont.ttf

fontawesome-webfont.ttf

766 ms

fontawesome-webfont.svg

fontawesome-webfont.svg

750 ms

Accessibility Review

url.cr accessibility score

69

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

url.cr best practices score

75

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

Page has valid source maps

SEO Factors

url.cr SEO score

83

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

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    ZH

  • Encoding

    UTF-8

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

url.cr

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