Ray.so Site Title
Create beautiful images of your code
Ray.so Meta Description
Turn your code into beautiful images. Choose from a range of syntax colors, hide or show the background, and toggle between a dark and light window.
Ray.so Test Results
Ray.so Mobile Performance: 46/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused JavaScript
Potential savings of 132 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.
Largest Contentful Paint element
8,160 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce JavaScript execution time
1.3 s
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.
Eliminate render-blocking resources
Potential savings of 130 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Avoid multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Serve static assets with an efficient cache policy
1 resource found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Insights
Document request latency
Your first network request is the most important. Reduce its latency by avoiding redirects, ensuring a fast server response, and enabling text compression.
Render blocking requests
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.
Max Potential First Input Delay
760 ms
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.
Time to Interactive
8.2 s
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.
Ray.so Mobile SEO: 100/100
Quick overview:
Ray.so Mobile Best Practices: 79/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being served over HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more about HTTPS.
General
Missing source maps for large first-party JavaScript
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.
Browser errors were logged to the console
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
Ray.so Mobile Accessibility: 85/100
Quick overview:
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Buttons do not have an accessible name
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.
Contrast
These are opportunities to improve the legibility of your content.
Background and foreground colors do not have a sufficient contrast ratio.
Low-contrast text is difficult or impossible for many users to read. Learn how to provide sufficient color contrast.
Similar sites
Similar tests
www.ray.com
www.ray.net
www.ray.org
www.ray.info
www.ray.biz
www.ray.us
www.ray.mobi
www.ay.so
www.ray.so
www.eay.so
www.reay.so
www.eray.so
www.day.so
www.rday.so
www.dray.so
www.fay.so
www.rfay.so
www.fray.so
www.tay.so
www.rtay.so
www.tray.so
www.ry.so
www.rqy.so
www.raqy.so
www.rqay.so
www.rwy.so
www.rawy.so
www.rway.so
www.rsy.so
www.rasy.so
www.rsay.so
www.rzy.so
www.razy.so
www.rzay.so
www.ra.so
www.rat.so
www.rayt.so
www.raty.so
www.rag.so
www.rayg.so
www.ragy.so
www.rah.so
www.rayh.so
www.rahy.so
www.rau.so
www.rayu.so
www.rauy.so
www.ray.net
www.ray.org
www.ray.info
www.ray.biz
www.ray.us
www.ray.mobi
www.ay.so
www.ray.so
www.eay.so
www.reay.so
www.eray.so
www.day.so
www.rday.so
www.dray.so
www.fay.so
www.rfay.so
www.fray.so
www.tay.so
www.rtay.so
www.tray.so
www.ry.so
www.rqy.so
www.raqy.so
www.rqay.so
www.rwy.so
www.rawy.so
www.rway.so
www.rsy.so
www.rasy.so
www.rsay.so
www.rzy.so
www.razy.so
www.rzay.so
www.ra.so
www.rat.so
www.rayt.so
www.raty.so
www.rag.so
www.rayg.so
www.ragy.so
www.rah.so
www.rayh.so
www.rahy.so
www.rau.so
www.rayu.so
www.rauy.so