Tools & Wizards About Us
upset.dev screenshot

Report Summary

  • 98

    Performance

    Renders faster than
    95% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

upset.dev

Frans Allen - Founder, Software Engineer, Speaker

Page Load Speed

1.3 sec in total

First Response

138 ms

Resources Loaded

886 ms

Page Rendered

257 ms

upset.dev screenshot

About Website

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.dev

Key Findings

We analyzed Upset.dev page load time and found that the first response time was 138 ms and then it took 1.1 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

upset.dev performance score

98

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.3 s

98/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

93/100

25%

SI (Speed Index)

Value1.3 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.1 s

99/100

10%

Network Requests Diagram

upset.dev

138 ms

upset.dev

68 ms

a9888b838b9b43b3.css

39 ms

app

49 ms

polyfills-c67a75d1b6f99dc8.js

65 ms

Our browser made a total of 25 requests to load all elements on the main page. We found that 92% of them (23 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 (580 ms) relates to the external source Ghchart.rshah.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 106.8 kB (80%)

Content Size

133.5 kB

After Optimization

26.7 kB

  • HTML
  • Images

In fact, the total size of Upset.dev main page is 133.5 kB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only 5% of websites need less resources to load. HTML takes 122.8 kB which makes up the majority of the site volume.

HTML Optimization

-87%

Potential reduce by 106.7 kB

  • Original 122.8 kB
  • After minification 122.8 kB
  • After compression 16.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. 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.7 kB or 87% of the original size.

Image Optimization

-1%

Potential reduce by 117 B

  • Original 10.7 kB
  • After minification 10.6 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. Upset images are well optimized though.

Requests Breakdown

Number of requests can be reduced by 10 (43%)

Requests Now

23

After Optimization

13

  • Images
  • JavaScript
  • CSS

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.

Network Requests Diagram

upset.dev

upset.dev

138 ms

upset.dev

upset.dev

68 ms

a9888b838b9b43b3.css

a9888b838b9b43b3.css

39 ms

app

app

49 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

65 ms

webpack-ae88b444f1e269b8.js

webpack-ae88b444f1e269b8.js

17 ms

2443530c-423ca43a8a11f4c6.js

2443530c-423ca43a8a11f4c6.js

38 ms

139-976cf27e540aef43.js

139-976cf27e540aef43.js

34 ms

main-app-c0fde4ac3a0b3bab.js

main-app-c0fde4ac3a0b3bab.js

29 ms

fransallen

fransallen

580 ms

icon-statically.svg

icon-statically.svg

46 ms

icon-puredns.svg

icon-puredns.svg

31 ms

icon-favicone.svg

icon-favicone.svg

32 ms

icon-blobcdn.svg

icon-blobcdn.svg

33 ms

icon-indiwtf.svg

icon-indiwtf.svg

39 ms

icon-fonts.svg

icon-fonts.svg

38 ms

image

image

187 ms

image

image

124 ms

image

image

115 ms

image

image

123 ms

image

image

188 ms

image

image

198 ms

image

image

196 ms

icon-digitalocean.svg

icon-digitalocean.svg

184 ms

icon-vultr.svg

icon-vultr.svg

186 ms

Accessibility Review

upset.dev accessibility score

96

Accessibility Issues

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

Links do not have a discernible name

Best Practices

upset.dev 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

SEO Factors

upset.dev SEO score

100

Search Engine Optimization Advices

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

Social Sharing Optimization

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: