Tools & Wizards About Us

Report Summary

  • 60

    Performance

    Renders faster than
    75% of other websites

  • 69

    Accessibility

    Visual factors better than
    that of 34% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

prettylinks.com

Pretty Links | Custom Link Shortener, Branded Link Management

Page Load Speed

1.8 sec in total

First Response

107 ms

Resources Loaded

1 sec

Page Rendered

644 ms

About Website

Click here to check amazing Pretty Links content for United States. Otherwise, check out these important facts you probably never knew about prettylinks.com

Pretty Links is a WordPress plugin URL shortener, link cloaker, branded link, and QR code generator to shrink, cloak, track, organize, and test all your links.

Visit prettylinks.com

Key Findings

We analyzed Prettylinks.com page load time and found that the first response time was 107 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.

Performance Metrics

prettylinks.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

44/100

10%

LCP (Largest Contentful Paint)

Value6.4 s

10/100

25%

SI (Speed Index)

Value4.2 s

78/100

10%

TBT (Total Blocking Time)

Value230 ms

87/100

30%

CLS (Cumulative Layout Shift)

Value0.034

100/100

15%

TTI (Time to Interactive)

Value8.6 s

37/100

10%

Network Requests Diagram

prettylinks.com

107 ms

prettylinks.com

51 ms

js

53 ms

memberpress.min.css

24 ms

widget-default.css

43 ms

Our browser made a total of 79 requests to load all elements on the main page. We found that 86% of them (68 requests) were addressed to the original Prettylinks.com, 6% (5 requests) were made to Use.typekit.net and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (381 ms) relates to the external source A.omappapi.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 112.1 kB (10%)

Content Size

1.2 MB

After Optimization

1.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Prettylinks.com 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. 65% of websites need less resources to load. Images take 728.5 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 110.9 kB

  • Original 142.4 kB
  • After minification 142.4 kB
  • After compression 31.5 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 110.9 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 728.5 kB
  • After minification 728.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. Pretty Links images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 642 B

  • Original 132.0 kB
  • After minification 132.0 kB
  • After compression 131.4 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 510 B

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

Requests Breakdown

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

Requests Now

68

After Optimization

27

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

Accessibility Review

prettylinks.com accessibility score

69

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

High

button, link, and menuitem elements do not have accessible names.

High

ARIA input fields do not have accessible names

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

prettylinks.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

prettylinks.com SEO score

79

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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 Prettylinks.com 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 Prettylinks.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

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