2 sec in total
89 ms
1.3 sec
665 ms
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.comWe analyzed Prettylinks.com page load time and found that the first response time was 89 ms and then it took 1.9 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.
prettylinks.com performance score
name
value
score
weighting
Value3.4 s
38/100
10%
Value7.9 s
3/100
25%
Value4.7 s
68/100
10%
Value470 ms
60/100
30%
Value0.233
54/100
15%
Value9.0 s
33/100
10%
89 ms
103 ms
71 ms
44 ms
36 ms
Our browser made a total of 82 requests to load all elements on the main page. We found that 76% of them (62 requests) were addressed to the original Prettylinks.com, 6% (5 requests) were made to Use.typekit.net and 4% (3 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (750 ms) relates to the external source Googleads.g.doubleclick.net.
Page size can be reduced by 74.9 kB (8%)
974.3 kB
899.4 kB
In fact, the total size of Prettylinks.com main page is 974.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 468.2 kB which makes up the majority of the site volume.
Potential reduce by 65.0 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 65.0 kB or 78% of the original size.
Potential reduce by 883 B
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.
Potential reduce by 3.7 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.
Potential reduce by 5.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.
Number of requests can be reduced by 49 (70%)
70
21
The browser has sent 70 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 27 to 1 for JavaScripts and from 24 to 1 for CSS and as a result speed up the page load time.
prettylinks.com
89 ms
prettylinks.com
103 ms
js
71 ms
wp-emoji-release.min.js
44 ms
widget-default.css
36 ms
theme.css
161 ms
style.min.css
171 ms
style.css
46 ms
all.min.css
166 ms
v4-shims.min.css
55 ms
672-layout.css
66 ms
font-awesome-animated.min.css
69 ms
styles.css
68 ms
prism.css
74 ms
toastr.min.css
74 ms
semantic.min.css
76 ms
css
56 ms
kb-frontend-app.css
111 ms
jquery.magnificpopup.min.css
103 ms
bootstrap.min.css
103 ms
skin-62a8021ad7654.css
154 ms
style.css
158 ms
prettylinks.com
171 ms
css
67 ms
frontend-gtag.min.js
179 ms
jquery.min.js
165 ms
jquery-migrate.min.js
178 ms
imagesloaded.min.js
168 ms
yqy0pbg.js
101 ms
prettylinks.com
200 ms
style.css
278 ms
dashicons.min.css
276 ms
thickbox.css
221 ms
672-layout.js
195 ms
prism.js
221 ms
semantic.min.js
220 ms
toastr.js
274 ms
kb-frontend-app.bundle.js
273 ms
0b16fd1b-e506-43f6-98b0-368eac27f332.js
162 ms
jquery.ba-throttle-debounce.min.js
360 ms
jquery.magnificpopup.min.js
273 ms
bootstrap.min.js
275 ms
theme.min.js
276 ms
app.js
271 ms
front_end_js.js
445 ms
thickbox.js
261 ms
helper.min.js
250 ms
analytics.js
51 ms
js
45 ms
conversion_async.js
140 ms
linkid.js
75 ms
laptop.svg
323 ms
pretty-links-screen-300x188.png
325 ms
iStock-950190050.jpg
322 ms
pat_flynn-300x300.png
403 ms
luria_petrucci-300x300.png
399 ms
daniel_j_lewis-300x300.png
402 ms
iStock-532666455-2.jpg
325 ms
api.min.js
141 ms
cp-pretty-links-header.jpg
301 ms
pretty-links-logo-color-white.svg
374 ms
button-play.png
377 ms
cp-pretty-links-testimonials.jpg
379 ms
diagonal-testimonial-top.svg
639 ms
diagonal-testimonial-bottom.svg
632 ms
icon-arrow-to-top.svg
636 ms
logo-pretty-links-white.svg
639 ms
diagonal-header-bottom.svg
639 ms
collect
250 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aXw.woff
297 ms
JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aXw.woff
550 ms
fa-solid-900.woff
669 ms
fa-regular-400.woff
670 ms
fa-brands-400.woff
725 ms
750 ms
clipboard.min.js
691 ms
d
78 ms
d
330 ms
d
340 ms
d
450 ms
p.gif
506 ms
loadingAnimation.gif
34 ms
prettylinks.com accessibility score
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
[aria-*] attributes do not match their roles
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
[aria-*] attributes do not have valid values
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
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
Links do not have a discernible name
prettylinks.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
prettylinks.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
Links do not have descriptive text
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
EN
EN
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.
prettylinks.com
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: