Basis.gold Site Title

Basis Gold Interface

Basis.gold Test Results

Basis.gold Mobile Performance: 33/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Remove unused JavaScript. Potential savings of 336 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Eliminate render-blocking resources. Potential savings of 1,230 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 5 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
5.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
5.1 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Keep request counts low and transfer sizes small
28 requests • 652 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid chaining critical requests
5 chains 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 large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid long main-thread tasks
4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More

Basis.gold Mobile SEO: 85/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
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.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.

Basis.gold Mobile Best Practices: 86/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 servedover 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.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
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.
Basis.gold Mobile Progressive Web App: 36/100
Quick overview:
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. The start_url did respond, but not via a service worker.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Page load is not fast enough on mobile networks
Interactive at 10.6 s
A fast page load over a cellular network ensures a good mobile user experience. Learn more. Your page loads too slowly and is not interactive within 10 seconds. Look at the opportunities and diagnostics in the "Performance" section to learn how to improve.
PWA Optimized
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 380px does not match the window size of 360px.
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.
Installable
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.
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 servedover 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.
Basis.gold Mobile Accessibility: 83/100
Quick overview:
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.
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.
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.
Similar tests
www.basis.com
www.basis.net
www.basis.org
www.basis.info
www.basis.biz
www.basis.us
www.basis.mobi
www.asis.gold
www.basis.gold
www.vasis.gold
www.bvasis.gold
www.vbasis.gold
www.gasis.gold
www.bgasis.gold
www.gbasis.gold
www.hasis.gold
www.bhasis.gold
www.hbasis.gold
www.nasis.gold
www.bnasis.gold
www.nbasis.gold
www.bsis.gold
www.bqsis.gold
www.baqsis.gold
www.bqasis.gold
www.bwsis.gold
www.bawsis.gold
www.bwasis.gold
www.bssis.gold
www.bassis.gold
www.bsasis.gold
www.bzsis.gold
www.bazsis.gold
www.bzasis.gold
www.bais.gold
www.bawis.gold
www.baswis.gold
www.baeis.gold
www.baseis.gold
www.baesis.gold
www.badis.gold
www.basdis.gold
www.badsis.gold
www.bazis.gold
www.baszis.gold
www.baxis.gold
www.basxis.gold
www.baxsis.gold
www.baais.gold
www.basais.gold
www.baasis.gold
www.bass.gold
www.basus.gold
www.basius.gold
www.basuis.gold
www.basjs.gold
www.basijs.gold
www.basjis.gold
www.basks.gold
www.basiks.gold
www.baskis.gold
www.basos.gold
www.basios.gold
www.basois.gold
www.basi.gold
www.basiw.gold
www.basisw.gold
www.basiws.gold
www.basie.gold
www.basise.gold
www.basies.gold
www.basid.gold
www.basisd.gold
www.basids.gold
www.basiz.gold
www.basisz.gold
www.basizs.gold
www.basix.gold
www.basisx.gold
www.basixs.gold
www.basia.gold
www.basisa.gold
www.basias.gold
Last Tested: