1.7 sec in total
12 ms
649 ms
1.1 sec
Visit short.io now to see the best up-to-date Short content for India and also check out these interesting facts you probably never knew about short.io
Short.io makes short links (vanity urls) on your own domain. Free signup, analytics and API. Chrome, slack, zapier and segment integrations.
Visit short.ioWe analyzed Short.io page load time and found that the first response time was 12 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 30% of websites can load faster.
short.io performance score
name
value
score
weighting
Value2.4 s
70/100
10%
Value5.4 s
20/100
25%
Value4.9 s
65/100
10%
Value1,850 ms
9/100
30%
Value0.213
58/100
15%
Value14.9 s
8/100
10%
12 ms
53 ms
102 ms
228 ms
82 ms
Our browser made a total of 57 requests to load all elements on the main page. We found that 68% of them (39 requests) were addressed to the original Short.io, 5% (3 requests) were made to Cdn.iubenda.com and 4% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (270 ms) belongs to the original domain Short.io.
Page size can be reduced by 533.9 kB (59%)
908.4 kB
374.5 kB
In fact, the total size of Short.io main page is 908.4 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. 70% of websites need less resources to load. HTML takes 634.3 kB which makes up the majority of the site volume.
Potential reduce by 400.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 400.5 kB or 63% of the original size.
Potential reduce by 133.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 133.4 kB or 49% of the original size.
Number of requests can be reduced by 24 (47%)
51
27
The browser has sent 51 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Short. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 25 to 1 for JavaScripts and as a result speed up the page load time.
short.io
12 ms
short.io
53 ms
lm.js
102 ms
api.js
228 ms
gtm.js
82 ms
star-878359938bfca8ac11baa364b3fbf1f0.svg
45 ms
hero-ef516402cc214bea4093f85c54047ffc.png
64 ms
small-planet-cd92bb46373721621fc50fa0c7350104.png
50 ms
universal-music-group-e81c2512783b9e63b6b8f41f952688b1.svg
50 ms
xhr.html
215 ms
polyfill-8323541ae364849595b4.js
52 ms
component---src-pages-index-js-99084b8cfa9ed2660f19.js
50 ms
33f35d011be7f60e35ffd6aece40e573709a40b5-a6c962a65c9ed03b1a07.js
44 ms
e425787ba0af1a563731dcf9249503ab8bb52501-a5c5ba37489e8a94ff90.js
58 ms
503877ba193b5e945a836ae3fa1d331563303179-6da64a406c788dfb11a3.js
59 ms
ed1465542c25d94136a7132dceb0172ac5ec56b4-257d2a855f26c5b9528f.js
58 ms
ea88be26-44c253138187bb2bddd0.js
61 ms
styles-407fe62976dc5310c43e.js
62 ms
app-66715550f7f1094a8ccc.js
84 ms
framework-17f6323ee71fbbb86feb.js
80 ms
webpack-runtime-d50b0cca4894eaac3a84.js
83 ms
raspberry-pi-abfdf59ad570a2a5a76593bb9b90a997.svg
80 ms
stats-f460a00bfca1a5f0adba0870cb4985fd.svg
82 ms
stats-ef413f85aa86d0d4eb9a7d18298d51d6.svg
83 ms
api-dbd2463cb4a9d1812c3e9764b143ba3a.svg
195 ms
domains-81af5411bbfe7dd7f18040bbfa3a93ea.svg
198 ms
teams-1a90a3041d9dedd5a113b14b0bed4cbb.png
203 ms
chat-578ecd265d2b2061c76b5bfe073302e0.svg
200 ms
support-background-fe5f48c014f3880dbe58b02f00acaca5.png
205 ms
medium-03-960e5daa255bdf37fa6ba9699df4f2a9.png
204 ms
medium-02-702c30ab29241670c96e416b76840094.png
203 ms
03-344f54aace4756a45fcf5b4920e65b83.svg
206 ms
update-1-d4c46c2a5a67dc3a6c194908af876909.png
211 ms
update-2-27b23ececaf908f25d0a70a61fa88f30.png
209 ms
update-3-4f9f2c07aaba51bea593abb4c919f60a.png
270 ms
medium-footer-691e8deab73f690d1ad14dd1233abb60.png
205 ms
Graphik-Regular-Web-9c8711499627177440d1bb4e49946533.woff2
196 ms
Graphik-Medium-Web-727adbffeb6b37513febdf0b57010d78.woff2
198 ms
Graphik-Semibold-Web-967958ba9a1b4bf0e2a213cd32317645.woff2
201 ms
js
178 ms
conversion_async.js
171 ms
bat.js
259 ms
stub.js
264 ms
amplitude-4.4.0-min.gz.js
235 ms
hotjar-1940192.js
253 ms
app-data.json
117 ms
page-data.json
81 ms
recaptcha__en.js
215 ms
214 ms
1239077767.json
50 ms
3280999885.json
52 ms
modules.7cb32ca5fc09d90486d4.js
150 ms
iubenda_cs.js
118 ms
box-25a418976ea02a6f393fbbe77cec94bb.html
105 ms
58 ms
core-en.js
29 ms
52677371.js
30 ms
short.io accessibility score
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
short.io 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
short.io 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
Document doesn't have a valid hreflang
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 Short.io 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 Short.io 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.
short.io
Open Graph description is not detected on the main page of Short. 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: