1.1 sec in total
133 ms
687 ms
236 ms
Welcome to upset.dev homepage info - get ready to check Upset best content right away, or after learning these important things about upset.dev
Frans Allen is a founder, software engineer, and speaker based in Yogyakarta, Indonesia. He is the creator of Statically and PureDNS.
Visit upset.devWe analyzed Upset.dev page load time and found that the first response time was 133 ms and then it took 923 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.
upset.dev performance score
name
value
score
weighting
Value1.3 s
98/100
10%
Value2.3 s
93/100
25%
Value1.3 s
100/100
10%
Value80 ms
99/100
30%
Value0.169
70/100
15%
Value2.8 s
97/100
10%
133 ms
35 ms
88 ms
28 ms
86 ms
Our browser made a total of 24 requests to load all elements on the main page. We found that 92% of them (22 requests) were addressed to the original Upset.dev, 4% (1 request) were made to Api-stack.vercel.app and 4% (1 request) were made to Ghchart.rshah.org. The less responsive or slowest element that took the longest time to load (404 ms) relates to the external source Ghchart.rshah.org.
Page size can be reduced by 107.6 kB (72%)
148.5 kB
40.9 kB
In fact, the total size of Upset.dev main page is 148.5 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. 25% of websites need less resources to load. HTML takes 123.0 kB which makes up the majority of the site volume.
Potential reduce by 106.8 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 106.8 kB or 87% of the original size.
Potential reduce by 767 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. Upset images are well optimized though.
Number of requests can be reduced by 5 (22%)
23
18
The browser has sent 23 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Upset. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 6 to 1 for JavaScripts and as a result speed up the page load time.
upset.dev
133 ms
b4b9fe8fb5bad261.css
35 ms
app
88 ms
polyfills-c67a75d1b6f99dc8.js
28 ms
webpack-03ad992658331270.js
86 ms
2443530c-423ca43a8a11f4c6.js
86 ms
139-976cf27e540aef43.js
86 ms
main-app-c0fde4ac3a0b3bab.js
83 ms
fransallen
404 ms
icon-statically.svg
28 ms
icon-puredns.svg
31 ms
icon-favicone.svg
34 ms
icon-blobcdn.svg
34 ms
icon-indiwtf.svg
32 ms
icon-fonts.svg
31 ms
image
103 ms
image
142 ms
image
108 ms
image
112 ms
image
117 ms
image
127 ms
image
193 ms
icon-digitalocean.svg
141 ms
icon-vultr.svg
138 ms
upset.dev accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
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
upset.dev best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
upset.dev 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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Upset.dev 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 Upset.dev 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.
upset.dev
Open Graph description is not detected on the main page of Upset. 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: