Skip to content
Audit Complete

Results for https://www.render.com

Visit site
Singapore Singapore · Singapore Completed: Apr 7, 2026 20:21 UTC

Mobile 375 × 812

Screenshot of the audited page (Mobile 375×812)

Desktop 1440 × 900

Screenshot of the audited page (Desktop 1440×900)
C73

Site Health

Score: 73 / 100

Based on 8 categories, 0 sections

How is this calculated?

The overall score is a weighted average of individual category scores. Categories with more impact on user experience and security carry more weight.

Performance 25%Security 25%Accessibility 15%SEO 10%Infrastructure 10%Compliance 8%Content 5%Sustainability 2%

Weights reflect general web best practices. Individual needs may differ.

Top Priorities (5)

1

Content-Security-Policy header is missing

Security › Security Headers
2

HSTS header is missing

Security › Security Headers
3

No Content-Security-Policy header found

Security › Content Security Policy
4

1 link(s) with no accessible text

Accessibility › Link & Button Quality
5

7 button(s) with no accessible text

Accessibility › Link & Button Quality
BeaverCheck badge
Embed this badge
[![BeaverCheck](https://beavercheck.com/badge?url=https%3A%2F%2Fwww.render.com)](https://beavercheck.com/results/f9f2f8c0-f28e-3b71-85ad-e9abb618e855)
<a href="https://beavercheck.com/results/f9f2f8c0-f28e-3b71-85ad-e9abb618e855"><img src="https://beavercheck.com/badge?url=https%3A%2F%2Fwww.render.com" alt="BeaverCheck Score"></a>
https://beavercheck.com/badge?url=https%3A%2F%2Fwww.render.com

This badge auto-updates with your latest scan result.

Was this report useful?

Thanks for your feedback!

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse.

31
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
84
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

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

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

6.59 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

3.43 s

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.168

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

25.26 s

Detailed Report

Audit breakdown by category with detailed findings.

31

Performance

Insights

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.

Layout shifts occur when elements move absent any user interaction. Investigate the causes of layout shifts, such as elements being added, removed, or their fonts changing as the page loads.

headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.16777399999999998] map[node:map[boundingRect:map[bottom:12497 height:1735 left:0 right:412 top:10762 width:412] lhId:page-1-DIV nodeLabel:FEATURES Autoscaling Private Networking Render Postgres Render Key Value Persis… path:1,HTML,1,BODY,2,DIV,0,MAIN,3,FOOTER,0,DIV,0,DIV selector:main.min-h-screen > footer.print:hidden > div.site-container > div.relative snippet:<div class="relative flex flex-col border-b-1 bg-grid bg-grid-border pt-[calc(100vw/8)…"> type:node] score:0.166464] map[node:map[boundingRect:map[bottom:329 height:48 left:320 right:339 top:281 width:18] lhId:page-2-DIV nodeLabel:div.space-y-40 > h1.font-roobert > div > div.inline-flex path:1,HTML,1,BODY,2,DIV,0,MAIN,2,DIV,1,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,H1,1,DIV,1,DIV selector:div.space-y-40 > h1.font-roobert > div > div.inline-flex snippet:<div class="inline-flex h-[1em] w-[0.6ch] items-center align-middle" style="opacity: 0;"> type:node] score:0.000744] map[node:map[boundingRect:map[bottom:329 height:48 left:320 right:339 top:281 width:18] lhId:page-2-DIV nodeLabel:div.space-y-40 > h1.font-roobert > div > div.inline-flex path:1,HTML,1,BODY,2,DIV,0,MAIN,2,DIV,1,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,H1,1,DIV,1,DIV selector:div.space-y-40 > h1.font-roobert > div > div.inline-flex snippet:<div class="inline-flex h-[1em] w-[0.6ch] items-center align-middle" style="opacity: 0;"> type:node] score:0.000277] map[node:map[boundingRect:map[bottom:329 height:48 left:320 right:339 top:281 width:18] lhId:page-2-DIV nodeLabel:div.space-y-40 > h1.font-roobert > div > div.inline-flex path:1,HTML,1,BODY,2,DIV,0,MAIN,2,DIV,1,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,H1,1,DIV,1,DIV selector:div.space-y-40 > h1.font-roobert > div > div.inline-flex snippet:<div class="inline-flex h-[1em] w-[0.6ch] items-center align-middle" style="opacity: 0;"> type:node] score:0.000162] map[node:map[boundingRect:map[bottom:329 height:48 left:320 right:339 top:281 width:18] lhId:page-2-DIV nodeLabel:div.space-y-40 > h1.font-roobert > div > div.inline-flex path:1,HTML,1,BODY,2,DIV,0,MAIN,2,DIV,1,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,H1,1,DIV,1,DIV selector:div.space-y-40 > h1.font-roobert > div > div.inline-flex snippet:<div class="inline-flex h-[1em] w-[0.6ch] items-center align-middle" style="opacity: 0;"> type:node] score:0.000127]]
headings: [map[key:node label:Element subItemsHeading:map[key:extra] valueType:node] map[granularity:0.001 key:score label:Layout shift score subItemsHeading:map[key:cause valueType:text] valueType:numeric]]
items: [map[node:map[type:text value:Total] score:0.001281] map[node:map[boundingRect:map[bottom:329 height:48 left:320 right:339 top:281 width:18] lhId:page-2-DIV nodeLabel:div.space-y-40 > h1.font-roobert > div > div.inline-flex path:1,HTML,1,BODY,2,DIV,0,MAIN,2,DIV,1,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,H1,1,DIV,1,DIV selector:div.space-y-40 > h1.font-roobert > div > div.inline-flex snippet:<div class="inline-flex h-[1em] w-[0.6ch] items-center align-middle" style="opacity: 0;"> type:node] score:0.000279] map[node:map[boundingRect:map[bottom:329 height:48 left:320 right:339 top:281 width:18] lhId:page-2-DIV nodeLabel:div.space-y-40 > h1.font-roobert > div > div.inline-flex path:1,HTML,1,BODY,2,DIV,0,MAIN,2,DIV,1,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,H1,1,DIV,1,DIV selector:div.space-y-40 > h1.font-roobert > div > div.inline-flex snippet:<div class="inline-flex h-[1em] w-[0.6ch] items-center align-middle" style="opacity: 0;"> type:node] score:0.000238] map[node:map[boundingRect:map[bottom:329 height:48 left:320 right:339 top:281 width:18] lhId:page-2-DIV nodeLabel:div.space-y-40 > h1.font-roobert > div > div.inline-flex path:1,HTML,1,BODY,2,DIV,0,MAIN,2,DIV,1,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,H1,1,DIV,1,DIV selector:div.space-y-40 > h1.font-roobert > div > div.inline-flex snippet:<div class="inline-flex h-[1em] w-[0.6ch] items-center align-middle" style="opacity: 0;"> type:node] score:0.000233] map[node:map[boundingRect:map[bottom:329 height:48 left:320 right:339 top:281 width:18] lhId:page-2-DIV nodeLabel:div.space-y-40 > h1.font-roobert > div > div.inline-flex path:1,HTML,1,BODY,2,DIV,0,MAIN,2,DIV,1,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,H1,1,DIV,1,DIV selector:div.space-y-40 > h1.font-roobert > div > div.inline-flex snippet:<div class="inline-flex h-[1em] w-[0.6ch] items-center align-middle" style="opacity: 0;"> type:node] score:0.000181] map[node:map[boundingRect:map[bottom:329 height:48 left:320 right:339 top:281 width:18] lhId:page-2-DIV nodeLabel:div.space-y-40 > h1.font-roobert > div > div.inline-flex path:1,HTML,1,BODY,2,DIV,0,MAIN,2,DIV,1,SECTION,1,DIV,1,DIV,0,DIV,0,DIV,0,H1,1,DIV,1,DIV selector:div.space-y-40 > h1.font-roobert > div > div.inline-flex snippet:<div class="inline-flex h-[1em] w-[0.6ch] items-center align-middle" style="opacity: 0;"> type:node] score:0.000165]]

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.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:36.835 source:map[column:64624 line:1 type:source-location url:https://render.com/_next/static/chunks/1255-d97305407b68a0cb.js?dpl=68486f5c88 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.286 source:map[column:9992 line:0 type:source-location url:https://render.com/_next/static/chunks/7853-467502e6b1f2ff83.js?dpl=h4q5z urlProvider:network]] map[reflowTime:17.382 source:map[column:31989 line:0 type:source-location url:https://render.com/_next/static/chunks/8363-c4be66d9e319c82d.js?dpl=h4q5z urlProvider:network]] map[reflowTime:19.167 source:map[column:1575 line:0 type:source-location url:https://render.com/_next/static/chunks/504-6b2b031492a11979.js?dpl=h4q5z urlProvider:network]]]

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.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

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.

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

These insights are also available in the Chrome DevTools Performance Panel - record a trace to view more detailed information.

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.

TTI

Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.

Estimated savings: 935 ms
URLTime Spent
www.render.com/935 ms
render.com/0.0 ms

These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS

ElementLayout shift score
FEATURES Autoscaling Private Networking Render Postgres Render Key Value Persis… main.min-h-screen > footer.print:hidden > div.site-container > div.relative
0.166
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.001
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000
div.space-y-40 > h1.font-roobert > div > div.inline-flex div.space-y-40 > h1.font-roobert > div > div.inline-flex
0.000

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.

Diagnostics

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.

Estimated savings: 150 ms 28.5 KiB
URLTransfer SizeEst Savings
render.com/_next/static/css/55033c4b37a2f447.css?dpl=68486f5c8833.1 KiB28.5 KiB

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

CategoryTime Spent
Script Evaluation7.0 s
Other2.6 s
Script Parsing & Compilation1.2 s
Style & Layout886 ms
Rendering337 ms
Garbage Collection217 ms
Parse HTML & CSS143 ms

Many navigations are performed by going back to a previous page, or forwards again. The back/forward cache (bfcache) can speed up these return navigations. Learn more about the bfcache

Failure reasonFailure type
The page was evicted from the cache because an active network connection received too much data. Chrome limits the amount of data that a page may receive while cached.Not actionable

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
div.divide-y > div.flex > div.relative > img.w-full div.divide-y > div.flex > div.relative > img.w-full
/images/hvk0tap5/production/f2f5b8978c63f1e90586db3b34e37...
div.grid > div.flex > div.relative > img.w-full div.grid > div.flex > div.relative > img.w-full
/images/hvk0tap5/production/6fa549bd2d5966949b3a3d827e58f...
div.grid > div.flex > div.relative > img.w-full div.grid > div.flex > div.relative > img.w-full
/images/hvk0tap5/production/ab65c00a2088d80ec286cea298b4a...
div.grid > div.flex > div.relative > img.w-full div.grid > div.flex > div.relative > img.w-full
/images/hvk0tap5/production/2d3e7c99d11549b2a9e69b4e926b2...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Optimize DOM size
Font display
Improve image delivery
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 7 user timings
Avoid long main-thread tasks 20 long tasks found
Avoid non-composited animations 2 animated elements found
Network Requests
Network Round Trip Times 10 ms
Server Backend Latencies 180 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 180 ms
INP breakdown
LCP request discovery
84

Accessibility

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.

Names and labels

When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.

Failing Elements
div.flex > div.max-md:min-h-[400px] > div.relative > button.shrink-0 div.flex > div.max-md:min-h-[400px] > div.relative > button.shrink-0
div.flex > div.max-md:min-h-[400px] > div.relative > button.shrink-0 div.flex > div.max-md:min-h-[400px] > div.relative > button.shrink-0

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
INSTANCE TYPE: div.relative > div.absolute > div.font-mono > span.text-gray-400
Autoscaling div.col-span-1 > ul.flex > li > a.ease
Private Networking div.col-span-1 > ul.flex > li > a.ease
Render Postgres div.col-span-1 > ul.flex > li > a.ease
Render Key Value div.col-span-1 > ul.flex > li > a.ease
Persistent Disks div.col-span-1 > ul.flex > li > a.ease
Infrastructure As Code div.col-span-1 > ul.flex > li > a.ease
Preview Environments div.col-span-1 > ul.flex > li > a.ease
Zero Downtime Deploys div.col-span-1 > ul.flex > li > a.ease
Render API div.col-span-1 > ul.flex > li > a.ease
Static Sites div.col-span-1 > ul.flex > li > a.ease
Web Services div.col-span-1 > ul.flex > li > a.ease
Private Services div.col-span-1 > ul.flex > li > a.ease
Background Workers div.col-span-1 > ul.flex > li > a.ease
Cron Jobs div.col-span-1 > ul.flex > li > a.ease
Render Postgres div.col-span-1 > ul.flex > li > a.ease
Render Key Value div.col-span-1 > ul.flex > li > a.ease
Deploy Docker Images div.col-span-1 > ul.flex > li > a.ease
Blog div.col-span-1 > ul.flex > li > a.ease
Changelog div.col-span-1 > ul.flex > li > a.ease
Docs div.col-span-1 > ul.flex > li > a.ease
Pricing div.col-span-1 > ul.flex > li > a.ease
Render for Startups div.col-span-1 > ul.flex > li > a.ease
Articles div.col-span-1 > ul.flex > li > a.ease
Security div.col-span-1 > ul.flex > li > a.ease
Community div.col-span-1 > ul.flex > li > a.ease
Privacy Policy div.col-span-1 > ul.flex > li > a.ease
DMCA Policy div.col-span-1 > ul.flex > li > a.ease
DPA div.col-span-1 > ul.flex > li > a.ease
Acceptable Use div.col-span-1 > ul.flex > li > a.ease
Terms of Use div.col-span-1 > ul.flex > li > a.ease
About div.col-span-1 > ul.flex > li > a.ease
Careers div.col-span-1 > ul.flex > li > a.ease
Brand Kit div.col-span-1 > ul.flex > li > a.ease
Press div.col-span-1 > ul.flex > li > a.ease
Contact div.col-span-1 > ul.flex > li > a.ease

These are opportunities to improve the legibility of your content.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Image elements have `[alt]` attributes
ARIA attributes are used as specified for the element's role
`[aria-hidden="true"]` elements do not contain focusable descendents
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
Lists contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`[lang]` attributes have a valid value
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
Loading the script 'https://us-assets.i.posthog.com/static/array.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.osano.com https://scout-cdn.salesloft.com https://snap.licdn.com https://www.google.com https://www.googletagmanager.com https://www.gstatic.com". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
100

SEO

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.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Lighthouse Scores

Industry-standard audits powered by Google Lighthouse. — Desktop

69
Performance Overall performance score (0–100) based on Core Web Vitals and other metrics. 90+ is good.
83
Accessibility Measures how accessible the page is for users with disabilities. Checks color contrast, ARIA labels, and semantic HTML.
92
Best Practices Checks for modern web development best practices including HTTPS, no console errors, and secure JavaScript.
100
SEO Measures basic SEO optimizations: meta tags, crawlability, link text, and mobile friendliness.

Core Web Vitals

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.

899 ms

Largest Contentful Paint Largest Contentful Paint — how long until the largest visible element loads. Under 2.5s is good.

1.70 s

Total Blocking Time Total Blocking Time — total time the main thread was blocked, preventing user input. Under 200ms is good.

363 ms

Cumulative Layout Shift Cumulative Layout Shift — measures visual stability. How much the page layout shifts during loading. Under 0.1 is good.

0.001

Speed Index Speed Index — how quickly content is visually displayed during load. Under 3.4s is good.

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

5.36 s

Detailed Report

Audit breakdown by category with detailed findings.

69

Performance

Insights

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.

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.

headings: [map[key:source label:Top function call valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:52.556 source:map[column:64624 line:1 type:source-location url:https://render.com/_next/static/chunks/1255-d97305407b68a0cb.js?dpl=68486f5c88 urlProvider:network]]]
headings: [map[key:source label:Source valueType:source-location] map[granularity:1 key:reflowTime label:Total reflow time valueType:ms]]
items: [map[reflowTime:0.309 source:map[column:10035 line:0 type:source-location url:https://render.com/_next/static/chunks/7853-467502e6b1f2ff83.js?dpl=h4q5z urlProvider:network]] map[reflowTime:25.061 source:map[column:31989 line:0 type:source-location url:https://render.com/_next/static/chunks/8363-c4be66d9e319c82d.js?dpl=h4q5z urlProvider:network]] map[reflowTime:27.186 source:map[column:1575 line:0 type:source-location url:https://render.com/_next/static/chunks/504-6b2b031492a11979.js?dpl=h4q5z urlProvider:network]]]

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.

description: [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints help the browser establish a connection earlier in the page load, saving time when the first request for that origin is made. The following are the origins that the page preconnected to.
title: Preconnected origins
value: no origins were preconnected
description: Add [preconnect](https://developer.chrome.com/docs/lighthouse/performance/uses-rel-preconnect/) hints to your most important origins, but try to use no more than 4.
title: Preconnect candidates
value: No additional origins are good candidates for preconnecting

A long cache lifetime can speed up repeat visits to your page. Learn more about caching.

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.

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.

Estimated savings: 405 ms
URLTime Spent
www.render.com/405 ms
render.com/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.

TTI

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.

Diagnostics

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.

Estimated savings: 40 ms 27.1 KiB
URLTransfer SizeEst Savings
render.com/_next/static/css/55033c4b37a2f447.css?dpl=68486f5c8833.1 KiB27.1 KiB

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

CategoryTime Spent
Script Evaluation2.0 s
Other869 ms
Style & Layout584 ms
Script Parsing & Compilation360 ms
Rendering188 ms
Garbage Collection71 ms
Parse HTML & CSS43 ms

Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions

URL
div.divide-y > div.flex > div.relative > img.w-full div.divide-y > div.flex > div.relative > img.w-full
/images/hvk0tap5/production/f2f5b8978c63f1e90586db3b34e37...
div.grid > div.flex > div.relative > img.w-full div.grid > div.flex > div.relative > img.w-full
/images/hvk0tap5/production/6fa549bd2d5966949b3a3d827e58f...
div.grid > div.flex > div.relative > img.w-full div.grid > div.flex > div.relative > img.w-full
/images/hvk0tap5/production/ab65c00a2088d80ec286cea298b4a...
div.grid > div.flex > div.relative > img.w-full div.grid > div.flex > div.relative > img.w-full
/images/hvk0tap5/production/2d3e7c99d11549b2a9e69b4e926b2...

More information about the performance of your application. These numbers don't directly affect the Performance score.

Layout shift culprits
Optimize DOM size
Font display
Improve image delivery
LCP breakdown
Modern HTTP
Optimize viewport for mobile
Minify CSS
Minify JavaScript
User Timing marks and measures 7 user timings
Avoid long main-thread tasks 11 long tasks found
Avoid non-composited animations 1 animated element found
Page didn't prevent back/forward cache restoration
Network Requests
Network Round Trip Times 10 ms
Server Backend Latencies 200 ms
Tasks
Diagnostics
Metrics
Screenshot Thumbnails
Final Screenshot
Script Treemap Data
Resources Summary
Initial server response time was short Root document took 240 ms
Avoid large layout shifts 12 layout shifts found
INP breakdown
LCP request discovery
83

Accessibility

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.

ARIA

Focusable descendents within an `[aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. Learn how `aria-hidden` affects focusable elements.

Failing Elements
Platform Overview Workflows FEATURES Autoscaling Private Networking Persistent … nav.hidden > ul.flex > div.group/dropdown > div.ease

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.

Contrast

Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.

Failing Elements
INSTANCE TYPE: div.relative > div.absolute > div.font-mono > span.text-gray-400
Autoscaling div.col-span-1 > ul.flex > li > a.ease
Private Networking div.col-span-1 > ul.flex > li > a.ease
Render Postgres div.col-span-1 > ul.flex > li > a.ease
Render Key Value div.col-span-1 > ul.flex > li > a.ease
Persistent Disks div.col-span-1 > ul.flex > li > a.ease
Infrastructure As Code div.col-span-1 > ul.flex > li > a.ease
Preview Environments div.col-span-1 > ul.flex > li > a.ease
Zero Downtime Deploys div.col-span-1 > ul.flex > li > a.ease
Render API div.col-span-1 > ul.flex > li > a.ease
Static Sites div.col-span-1 > ul.flex > li > a.ease
Web Services div.col-span-1 > ul.flex > li > a.ease
Private Services div.col-span-1 > ul.flex > li > a.ease
Background Workers div.col-span-1 > ul.flex > li > a.ease
Cron Jobs div.col-span-1 > ul.flex > li > a.ease
Render Postgres div.col-span-1 > ul.flex > li > a.ease
Render Key Value div.col-span-1 > ul.flex > li > a.ease
Deploy Docker Images div.col-span-1 > ul.flex > li > a.ease
Blog div.col-span-1 > ul.flex > li > a.ease
Changelog div.col-span-1 > ul.flex > li > a.ease
Docs div.col-span-1 > ul.flex > li > a.ease
Pricing div.col-span-1 > ul.flex > li > a.ease
Render for Startups div.col-span-1 > ul.flex > li > a.ease
Articles div.col-span-1 > ul.flex > li > a.ease
Security div.col-span-1 > ul.flex > li > a.ease
Community div.col-span-1 > ul.flex > li > a.ease
Privacy Policy div.col-span-1 > ul.flex > li > a.ease
DMCA Policy div.col-span-1 > ul.flex > li > a.ease
DPA div.col-span-1 > ul.flex > li > a.ease
Acceptable Use div.col-span-1 > ul.flex > li > a.ease
Terms of Use div.col-span-1 > ul.flex > li > a.ease
About div.col-span-1 > ul.flex > li > a.ease
Careers div.col-span-1 > ul.flex > li > a.ease
Brand Kit div.col-span-1 > ul.flex > li > a.ease
Press div.col-span-1 > ul.flex > li > a.ease
Contact div.col-span-1 > ul.flex > li > a.ease

These are opportunities to improve the legibility of your content.

Tables and lists

Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.

Failing Elements
Product Platform Overview Workflows FEATURES Autoscaling Private Networking Per… div.site-container > div.flex > nav.hidden > ul.flex

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Best practices

Disabling zooming is problematic for users with low vision who rely on screen magnification to properly see the contents of a web page. Learn more about the viewport meta tag.

Failing Elements
head > meta head > meta

These items highlight common accessibility best practices.

Interactive controls are keyboard focusable
Interactive elements indicate their purpose and state
The page has a logical tab order
Visual order on the page follows DOM order
User focus is not accidentally trapped in a region
The user's focus is directed to new content added to the page
HTML5 landmark elements are used to improve navigation
Offscreen content is hidden from assistive technology
Custom controls have associated labels
Custom controls have ARIA roles
`[aria-*]` attributes match their roles
`[aria-hidden="true"]` is not present on the document `<body>`
`[role]`s have all required `[aria-*]` attributes
`[role]` values are valid
`[aria-*]` attributes have valid values
`[aria-*]` attributes are valid and not misspelled
Buttons have an accessible name
Image elements have `[alt]` attributes
ARIA attributes are used as specified for the element's role
Elements use only permitted ARIA attributes
Document has a `<title>` element
`<html>` element has a `[lang]` attribute
`<html>` element has a valid value for its `[lang]` attribute
Links have a discernible name
List items (`<li>`) are contained within `<ul>`, `<ol>` or `<menu>` parent elements
Touch targets have sufficient size and spacing.
`[lang]` attributes have a valid value
Heading elements appear in a sequentially-descending order
Document has a main landmark.
Deprecated ARIA roles were not used
Identical links have the same purpose.
`[accesskey]` values are unique
`button`, `link`, and `menuitem` elements have accessible names
Elements with `role="dialog"` or `role="alertdialog"` have accessible names.
ARIA input fields have accessible names
ARIA `meter` elements have accessible names
ARIA `progressbar` elements have accessible names
Elements with an ARIA `[role]` that require children to contain a specific `[role]` have all required children.
`[role]`s are contained by their required parent element
Elements with the `role=text` attribute do not have focusable descendents.
ARIA toggle fields have accessible names
ARIA `tooltip` elements have accessible names
ARIA `treeitem` elements have accessible names
The page contains a heading, skip link, or landmark region
`<dl>`'s contain only properly-ordered `<dt>` and `<dd>` groups, `<script>`, `<template>` or `<div>` elements.
Definition list items are wrapped in `<dl>` elements
ARIA IDs are unique
No form fields have multiple labels
`<frame>` or `<iframe>` elements have a title
`<html>` element has an `[xml:lang]` attribute with the same base language as the `[lang]` attribute.
Input buttons have discernible text.
`<input type="image">` elements have `[alt]` text
Form elements have associated labels
Links are distinguishable without relying on color.
The document does not use `<meta http-equiv="refresh">`
`<object>` elements have alternate text
Select elements have associated label elements.
Skip links are focusable.
No element has a `[tabindex]` value greater than 0
Cells in a `<table>` element that use the `[headers]` attribute refer to table cells within the same table.
`<th>` elements and elements with `[role="columnheader"/"rowheader"]` have data cells they describe.
`<video>` elements contain a `<track>` element with `[kind="captions"]`
Tables have different content in the summary attribute and `<caption>`.
All heading elements contain content.
Uses ARIA roles only on compatible elements
Image elements do not have `[alt]` attributes that are redundant text.
Elements with visible text labels have matching accessible names.
Tables use `<caption>` instead of cells with the `[colspan]` attribute to indicate a caption.
`<td>` elements in a large `<table>` have one or more table headers.
92

Best Practices

General

Errors logged to the console indicate unresolved problems. They can come from network request failures and other browser concerns. Learn more about this errors in console diagnostic audit

SourceDescription
Loading the script 'https://us-assets.i.posthog.com/static/array.js' violates the following Content Security Policy directive: "script-src 'self' 'unsafe-inline' 'unsafe-eval' https://*.osano.com https://scout-cdn.salesloft.com https://snap.licdn.com https://www.google.com https://www.googletagmanager.com https://www.gstatic.com". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback. The action has been blocked.

Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.

Issue type
Content security policy
Uses HTTPS
Avoids deprecated APIs
Avoids third-party cookies
Allows users to paste into input fields
Avoids requesting the geolocation permission on page load
Avoids requesting the notification permission on page load
Displays images with correct aspect ratio
Serves images with appropriate resolution
Page has the HTML doctype
Properly defines charset
Ensure CSP is effective against XSS attacks
Ensure proper origin isolation with COOP
Mitigate DOM-based XSS with Trusted Types
Detected JavaScript libraries
Redirects HTTP traffic to HTTPS
Use a strong HSTS policy
Mitigate clickjacking with XFO or CSP
100

SEO

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.

Structured data is valid
Page isn’t blocked from indexing
Document has a `<title>` element
Document has a meta description
Page has successful HTTP status code
Links have descriptive text
Links are crawlable
robots.txt is valid
Image elements have `[alt]` attributes
Document has a valid `hreflang`
Document has a valid `rel=canonical`

Send Feedback