Brightdata.com Test Results

Brightdata.com Mobile Performance: 30/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Reduce unused JavaScript. Potential savings of 460 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn more.
Minify JavaScript. Potential savings of 151 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Reduce unused CSS. Potential savings of 49 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn more.
Remove duplicate modules in JavaScript bundles. Potential savings of 23 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
Defer offscreen images. Potential savings of 4 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 48 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn More
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minimize main-thread work
16.4 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,640 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.
Reduce JavaScript execution time
7.2 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Serve static assets with an efficient cache policy
37 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid an excessive DOM size
1,150 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoid enormous network payloads
Total size was 2,755 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid chaining critical requests
1 chain found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Avoid non-composited animations
81 animated elements found
Animations which are not composited can be janky and increase CLS. Learn more
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Keep request counts low and transfer sizes small
406 requests • 2,755 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Brightdata.com Mobile SEO: 86/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.

Brightdata.com Mobile Best Practices: 80/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.
Includes front-end JavaScript libraries with known security vulnerabilities
19 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn more
General
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn more
Brightdata.com Mobile Progressive Web App: 42/100
Quick overview:
PWA Optimized
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
Service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
Brightdata.com Mobile Accessibility: 58/100
Quick overview:
ARIA
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.
Elements with an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
ARIA input fields do not have accessible names
When an input field doesn't have an accessible name, screen readers announce it with a generic name, making it unusable for users who rely on screen readers. Learn more.
`[role]`s are not contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more.
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.
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 more.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Image elements do not have `[alt]` attributes
Informative elements should aim for short, descriptive alternate text. Decorative elements can be ignored with an empty alt attribute. Learn more.
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 more.
Best practices
These items highlight common accessibility best practices.
`[user-scalable="no"]` is used in the `<meta name="viewport">` element or the `[maximum-scale]` attribute is less than 5.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. Learn more.
`[id]` attributes on active, focusable elements are not unique
All focusable elements must have a unique `id` to ensure that they're visible to assistive technologies. Learn more.
Similar sites
Similar tests
www.brightdata.com
www.brightdata.net
www.brightdata.org
www.brightdata.info
www.brightdata.biz
www.brightdata.us
www.brightdata.mobi
www.rightdata.com
www.brightdata.com
www.vrightdata.com
www.bvrightdata.com
www.vbrightdata.com
www.grightdata.com
www.bgrightdata.com
www.gbrightdata.com
www.hrightdata.com
www.bhrightdata.com
www.hbrightdata.com
www.nrightdata.com
www.bnrightdata.com
www.nbrightdata.com
www.bightdata.com
www.beightdata.com
www.breightdata.com
www.berightdata.com
www.bdightdata.com
www.brdightdata.com
www.bdrightdata.com
www.bfightdata.com
www.brfightdata.com
www.bfrightdata.com
www.btightdata.com
www.brtightdata.com
www.btrightdata.com
www.brghtdata.com
www.brughtdata.com
www.briughtdata.com
www.bruightdata.com
www.brjghtdata.com
www.brijghtdata.com
www.brjightdata.com
www.brkghtdata.com
www.brikghtdata.com
www.brkightdata.com
www.broghtdata.com
www.brioghtdata.com
www.broightdata.com
www.brihtdata.com
www.brifhtdata.com
www.brigfhtdata.com
www.brifghtdata.com
www.brivhtdata.com
www.brigvhtdata.com
www.brivghtdata.com
www.brithtdata.com
www.brigthtdata.com
www.britghtdata.com
www.bribhtdata.com
www.brigbhtdata.com
www.bribghtdata.com
www.briyhtdata.com
www.brigyhtdata.com
www.briyghtdata.com
www.brihhtdata.com
www.brighhtdata.com
www.brihghtdata.com
www.brigtdata.com
www.brigbtdata.com
www.brighbtdata.com
www.briggtdata.com
www.brighgtdata.com
www.brigghtdata.com
www.brigytdata.com
www.brighytdata.com
www.brigutdata.com
www.brighutdata.com
www.briguhtdata.com
www.brigjtdata.com
www.brighjtdata.com
www.brigjhtdata.com
www.brigntdata.com
www.brighntdata.com
www.brignhtdata.com
www.brighdata.com
www.brighrdata.com
www.brightrdata.com
www.brighrtdata.com
www.brighfdata.com
www.brightfdata.com
www.brighftdata.com
www.brighgdata.com
www.brightgdata.com
www.brighydata.com
www.brightydata.com
www.brightata.com
www.brightxata.com
www.brightdxata.com
www.brightxdata.com
www.brightsata.com
www.brightdsata.com
www.brightsdata.com
www.brighteata.com
www.brightdeata.com
www.brightedata.com
www.brightrata.com
www.brightdrata.com
www.brightfata.com
www.brightdfata.com
www.brightcata.com
www.brightdcata.com
www.brightcdata.com
www.brightdta.com
www.brightdqta.com
www.brightdaqta.com
www.brightdqata.com
www.brightdwta.com
www.brightdawta.com
www.brightdwata.com
www.brightdsta.com
www.brightdasta.com
www.brightdzta.com
www.brightdazta.com
www.brightdzata.com
www.brightdaa.com
www.brightdara.com
www.brightdatra.com
www.brightdarta.com
www.brightdafa.com
www.brightdatfa.com
www.brightdafta.com
www.brightdaga.com
www.brightdatga.com
www.brightdagta.com
www.brightdaya.com
www.brightdatya.com
www.brightdayta.com
www.brightdat.com
www.brightdatq.com
www.brightdataq.com
www.brightdatqa.com
www.brightdatw.com
www.brightdataw.com
www.brightdatwa.com
www.brightdats.com
www.brightdatas.com
www.brightdatsa.com
www.brightdatz.com
www.brightdataz.com
www.brightdatza.com
www.brightdata.con
Last Tested: