Brazil · Sao Paulo Completed: Apr 7, 2026 20:20 UTCMobile 375 × 812
Desktop 1440 × 900
Score: 73 / 100
Based on 8 categories, 0 sections
The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.
Weights reflect general web best practices. Individual needs may differ.
Content-Security-Policy header is missing
HSTS header is missing
No Content-Security-Policy header found
Page weighs 7.6 MB (4.9 MB transferred)
1 link(s) with no accessible text
[](https://beavercheck.com/results/c89eb169-36f5-6d32-428b-7fe0b0d43f5a)<a href="https://beavercheck.com/results/c89eb169-36f5-6d32-428b-7fe0b0d43f5a"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fly.io" alt="BeaverCheck Score"></a>https://beavercheck.com/badge?url=https%3A%2F%2Fwww.fly.ioThis badge auto-updates with your latest scan result.
Thanks for your feedback!
Industry-standard audits powered by Google Lighthouse.
Key metrics that affect user experience.
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
2.27 s
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
23.28 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
994 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
2.27 s
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
23.66 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| fly.io/phx/ui/fonts/fricolage-grotesque.var.woff2 | 0.0 ms | 143.2 KiB |
| fly.io/phx/ui/fonts/mackinac-bold-italic.woff2 | 0.0 ms | 26.2 KiB |
| fly.io/phx/ui/fonts/mackinac-bold.woff2 | 0.0 ms | 26.1 KiB |
| fly.io/phx/ui/fonts/mackinac-medium-italic.woff2 | 0.0 ms | 26.0 KiB |
| fly.io/phx/ui/fonts/fragment-mono-italic.woff2 | 0.0 ms | 25.8 KiB |
| fly.io/phx/ui/fonts/mackinac-medium.woff2 | 0.0 ms | 25.2 KiB |
| fly.io/phx/ui/fonts/fragment-mono-regular.woff2 | 0.0 ms | 24.9 KiB |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
A forced reflow occurs when JavaScript queries geometric properties (such as offsetWidth) after styles have been invalidated by a change to the DOM state. This can result in poor performance. Learn more about forced reflows and possible mitigations.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| URL | Resource Size | Est Savings | |
|---|---|---|---|
header.hero > div.absolute > picture > img.w-full header.hero > div.absolute > picture > img.w-full | fly.io/phx/images/new-home-hero-017530e15474786e3c428d4c739a9e2d.webp?vsn=d | 994.0 KiB | 946.5 KiB |
main > section.relative > div.relative > img.w-full main > section.relative > div.relative > img.w-full | fly.io/phx/images/home-6-779aa35b5c66e1acf0a892d23d0f89aa.webp?vsn=d | 764.0 KiB | 691.5 KiB |
main > section.relative > div.relative > img.w-full main > section.relative > div.relative > img.w-full | fly.io/phx/images/2-home-5715b50f553c9da9313168e80e43a36f.webp?vsn=d | 487.9 KiB | 433.2 KiB |
main > section.relative > div.relative > img.w-full main > section.relative > div.relative > img.w-full | fly.io/phx/images/5-home-83633deac598ae018df6c35e6a97d522.webp?vsn=d | 438.2 KiB | 365.7 KiB |
main > section.relative > div.relative > img.w-full main > section.relative > div.relative > img.w-full | fly.io/phx/images/3-home-1e977867026ea52093a83850ad96a4f0.webp?vsn=d | 418.3 KiB | 363.5 KiB |
main > section.relative > div.relative > img.w-full main > section.relative > div.relative > img.w-full | fly.io/phx/images/4-home-84e15e7b8209179b4ddbc60a917b97ba.webp?vsn=d | 224.8 KiB | 170.1 KiB |
section.relative > div.relative > div.lg:grid > img.w-full section.relative > div.relative > div.lg:grid > img.w-full | fly.io/phx/images/autoscale3-db93aeaddd7d758fcfe644548248427c.webp?vsn=d | 148.0 KiB | 109.2 KiB |
Supabase ul.shrink-0 > li.flex > a.flex-none > img.h-6 | fly.io/phx/images/supabase-533b3ab7b5869d39d98a9d79e4f7b664.png?vsn=d | 60.9 KiB | 60.4 KiB |
Mercor ul.shrink-0 > li.flex > a.flex-none > img.h-7 | fly.io/phx/images/mercor-a7ffc13de45fe6eff409813c0014675e.png?vsn=d | 19.9 KiB | 18.5 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
| URL | Transfer Size | Duration |
|---|---|---|
| fly.io/phx/assets/app-83570185e8a9c56eba0a1e85900db2eb.css?vsn=d | 88.5 KiB | 610 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
| URL | Time Spent |
|---|---|
| www.fly.io/ | 755 ms |
| fly.io/ | 0.0 ms |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
| URL | Transfer Size | Est Savings |
|---|---|---|
| fly.io/phx/assets/app-83570185e8a9c56eba0a1e85900db2eb.css?vsn=d | 88.2 KiB | 83.9 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| fly.io/phx/assets/js/app-8e481f8200d3ae9504da3cfa56ce2cfb.js?vsn=d | 496.2 KiB | 163.8 KiB |
| analytics.fly.io/gtag/js?id=G-EX6DMZ1DZV | 170.8 KiB | 64.2 KiB |
| analytics.fly.io/gtm.js?id=GTM-M35Q2HRQ | 118.6 KiB | 63.8 KiB |
| /gtag/js?id=G-XXXXXXXXXX&cx=c>m=4e6460h1&sign=e459c918b... | 134.9 KiB | 62.4 KiB |
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
| URL | Total CPU Time | Script Evaluation | Script Parse |
|---|---|---|---|
| fly.io/ | 917 ms | 22 ms | 5.9 ms |
| fly.io/phx/assets/js/app-8e481f8200d3ae9504da3cfa56ce2cfb.js?vsn=d | 717 ms | 464 ms | 214 ms |
| Unattributable | 592 ms | 39 ms | 0.0 ms |
| analytics.fly.io/gtag/js?id=G-EX6DMZ1DZV | 562 ms | 462 ms | 72 ms |
| /gtag/js?id=G-XXXXXXXXXX&cx=c>m=4e6460h1&sign=e459c918b... | 246 ms | 192 ms | 52 ms |
| analytics.fly.io/gtm.js?id=GTM-M35Q2HRQ | 124 ms | 67 ms | 45 ms |
| fly.io/phx/assets/app-83570185e8a9c56eba0a1e85900db2eb.css?vsn=d | 89 ms | 0.0 ms | 0.0 ms |
| fly.io/js/events.js | 51 ms | 23 ms | 0.9 ms |
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
| Category | Time Spent |
|---|---|
| Script Evaluation | 1.3 s |
| Other | 990 ms |
| Script Parsing & Compilation | 392 ms |
| Style & Layout | 379 ms |
| Rendering | 109 ms |
| Parse HTML & CSS | 99 ms |
| Garbage Collection | 66 ms |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| Link destination | Link Text |
|---|---|
| fly.io/docs/speedrun/ | Learn More |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Industry-standard audits powered by Google Lighthouse. — Desktop
Key metrics that affect user experience. — Desktop
First Contentful Paint First Contentful Paint — how long until the browser renders the first piece of content. Under 1.8s is good.
581 ms
Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.
3.61 s
Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.
86 ms
Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.
0.000
Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.
598 ms
Time to Interactive Time to Interactive — how long until the page is fully interactive and responds to user input. Under 3.8s is good.
3.76 s
Audit breakdown by category with detailed findings.
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Polyfills and transforms enable older browsers to use new JavaScript features. However, many aren't necessary for modern browsers. Consider modifying your JavaScript build process to not transpile Baseline features, unless you know you must support older browsers. Learn why most sites can deploy ES6+ code without transpiling
3rd party code can significantly impact load performance. Reduce and defer loading of 3rd party code to prioritize your page's content.
A long cache lifetime can speed up repeat visits to your page. Learn more about caching.
| Request | Cache TTL | Transfer Size |
|---|---|---|
| fly.io/phx/ui/fonts/fricolage-grotesque.var.woff2 | 0.0 ms | 143.2 KiB |
| fly.io/phx/ui/fonts/mackinac-bold-italic.woff2 | 0.0 ms | 26.2 KiB |
| fly.io/phx/ui/fonts/mackinac-bold.woff2 | 0.0 ms | 26.1 KiB |
| fly.io/phx/ui/fonts/mackinac-medium-italic.woff2 | 0.0 ms | 26.0 KiB |
| fly.io/phx/ui/fonts/fragment-mono-italic.woff2 | 0.0 ms | 25.8 KiB |
| fly.io/phx/ui/fonts/mackinac-medium.woff2 | 0.0 ms | 25.2 KiB |
| fly.io/phx/ui/fonts/fragment-mono-regular.woff2 | 0.0 ms | 24.9 KiB |
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Reducing the download time of images can improve the perceived load time of the page and LCP. Learn more about optimizing image size
| URL | Resource Size | Est Savings | |
|---|---|---|---|
header.hero > div.absolute > picture > img.w-full header.hero > div.absolute > picture > img.w-full | fly.io/phx/images/new-home-hero-017530e15474786e3c428d4c739a9e2d.webp?vsn=d | 994.0 KiB | 827.3 KiB |
main > section.relative > div.relative > img.w-full main > section.relative > div.relative > img.w-full | fly.io/phx/images/2-home-5715b50f553c9da9313168e80e43a36f.webp?vsn=d | 487.9 KiB | 469.6 KiB |
main > section.relative > div.relative > img.w-full main > section.relative > div.relative > img.w-full | fly.io/phx/images/5-home-83633deac598ae018df6c35e6a97d522.webp?vsn=d | 438.2 KiB | 414.0 KiB |
main > section.relative > div.relative > img.w-full main > section.relative > div.relative > img.w-full | fly.io/phx/images/3-home-1e977867026ea52093a83850ad96a4f0.webp?vsn=d | 418.3 KiB | 400.0 KiB |
main > section.relative > div.relative > img.w-full main > section.relative > div.relative > img.w-full | fly.io/phx/images/4-home-84e15e7b8209179b4ddbc60a917b97ba.webp?vsn=d | 224.8 KiB | 206.5 KiB |
section.relative > div.relative > div.lg:grid > img.w-full section.relative > div.relative > div.lg:grid > img.w-full | fly.io/phx/images/autoscale3-db93aeaddd7d758fcfe644548248427c.webp?vsn=d | 148.0 KiB | 135.0 KiB |
Optimize LCP by making the LCP image discoverable from the HTML immediately, and avoiding lazy-loading
HTTP/2 and HTTP/3 offer many benefits over HTTP/1.1, such as multiplexing. Learn more about using modern HTTP.
Avoid chaining critical requests by reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load.
Requests are blocking the page's initial render, which may delay LCP. Deferring or inlining can move these network requests out of the critical path.
| URL | Transfer Size | Duration |
|---|---|---|
| fly.io/phx/assets/app-83570185e8a9c56eba0a1e85900db2eb.css?vsn=d | 88.5 KiB | 128 ms |
These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
| URL | Time Spent |
|---|---|
| www.fly.io/ | 205 ms |
| fly.io/ | 0.0 ms |
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
| URL | Transfer Size | Est Savings |
|---|---|---|
| fly.io/phx/assets/app-83570185e8a9c56eba0a1e85900db2eb.css?vsn=d | 88.2 KiB | 82.2 KiB |
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
| URL | Transfer Size | Est Savings |
|---|---|---|
| fly.io/phx/assets/js/app-8e481f8200d3ae9504da3cfa56ce2cfb.js?vsn=d | 496.2 KiB | 163.8 KiB |
| /gtag/js?id=G-EX6DMZ1DZV&cx=c>m=4e6460h1&sign=00e7d94f8... | 171.0 KiB | 113.8 KiB |
| analytics.fly.io/gtag/js?id=G-EX6DMZ1DZV | 170.8 KiB | 66.0 KiB |
| /gtag/js?id=G-XXXXXXXXXX&cx=c>m=4e6460h1&sign=00e7d94f8... | 135.1 KiB | 63.4 KiB |
| analytics.fly.io/gtm.js?id=GTM-M35Q2HRQ | 118.6 KiB | 62.0 KiB |
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
More information about the performance of your application. These numbers don't directly affect the Performance score.
These checks highlight opportunities to improve the accessibility of your web app. Automatic detection can only detect a subset of issues and does not guarantee the accessibility of your web app, so manual testing is also encouraged.
When definition lists are not properly marked up, screen readers may produce confusing or inaccurate output. Learn how to structure definition lists correctly.
| Failing Elements |
|---|
Products
PRODUCTS
Machines
Sprites
Managed Postgres
Phoenix.new
FEATURES
Privat… header.navbar > nav.pointer-events-auto > div.hidden > dl.flex-none |
Articles
Blog
Phoenix Files
Laravel Bytes
Ruby Dispatch
Django Beats
JavaScript… header.navbar > nav.pointer-events-auto > div.hidden > dl.flex-none |
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
These checks ensure that your page is following basic search engine optimization advice. There are many additional factors Lighthouse does not score here that may affect your search ranking, including performance on Core Web Vitals. Learn more about Google Search Essentials.
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
| Link destination | Link Text |
|---|---|
| fly.io/docs/speedrun/ | Learn More |
Format your HTML in a way that enables crawlers to better understand your app’s content.
Send Feedback