2.3 sec in total
113 ms
1.2 sec
946 ms
Visit shortly.cc now to see the best up-to-date Shortly content for Tunisia and also check out these interesting facts you probably never knew about shortly.cc
Shorten URL, share it and tracking clicks for analytics. One short link, infinite possibilities!
Visit shortly.ccWe analyzed Shortly.cc page load time and found that the first response time was 113 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 40% of websites can load faster.
shortly.cc performance score
name
value
score
weighting
Value2.1 s
82/100
10%
Value3.1 s
76/100
25%
Value4.8 s
68/100
10%
Value2,050 ms
7/100
30%
Value0.019
100/100
15%
Value13.0 s
13/100
10%
113 ms
186 ms
77 ms
185 ms
111 ms
Our browser made a total of 31 requests to load all elements on the main page. We found that 48% of them (15 requests) were addressed to the original Shortly.cc, 29% (9 requests) were made to Cdnjs.cloudflare.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (557 ms) relates to the external source Analytics.infraops.info.
Page size can be reduced by 285.8 kB (69%)
411.8 kB
126.0 kB
In fact, the total size of Shortly.cc main page is 411.8 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. 35% of websites need less resources to load. CSS take 247.1 kB which makes up the majority of the site volume.
Potential reduce by 13.1 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.1 kB, which is 17% 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 13.1 kB or 75% of the original size.
Potential reduce by 66.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 66.7 kB or 45% of the original size.
Potential reduce by 205.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. Shortly.cc needs all CSS files to be minified and compressed as it can save up to 205.9 kB or 83% of the original size.
Number of requests can be reduced by 20 (74%)
27
7
The browser has sent 27 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Shortly. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 15 to 1 for JavaScripts and from 7 to 1 for CSS and as a result speed up the page load time.
shortly.cc
113 ms
shortly.cc
186 ms
bootstrap.min.css
77 ms
style.css
185 ms
components.min.css
111 ms
fa-all.min.css
115 ms
jquery.min.js
67 ms
bootstrap.min.js
289 ms
application.fn.js
125 ms
datepicker.min.js
88 ms
datepicker.min.css
106 ms
chosen.jquery.min.js
165 ms
icheck.min.js
170 ms
clipboard.min.js
163 ms
cookieconsent.min.js
134 ms
cookieconsent.min.css
170 ms
jquery.autocomplete.min.js
128 ms
pace.js
167 ms
css
100 ms
application.js
359 ms
server.js
355 ms
main.js
420 ms
analytics.js
390 ms
matomo.js
557 ms
auto_site_logo.png
393 ms
wave.png
393 ms
landing.png
393 ms
KFOmCnqEu92Fr1Mu4mxMKTU1Kg.woff
78 ms
glyphicons-halflings-regular.woff
63 ms
collect
66 ms
collect
47 ms
shortly.cc 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
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<frame> or <iframe> elements do not have a title
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
shortly.cc 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
Page has valid source maps
shortly.cc SEO score
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
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Shortly.cc 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 Shortly.cc 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.
shortly.cc
Open Graph data is detected on the main page of Shortly. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: