Baseus.vn Test Results

Baseus.vn Mobile Performance: 27/100
Quick overview:
Time to Interactive
19.0 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.
First Meaningful Paint
6.6 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Max Potential First Input Delay
430 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.

Baseus.vn Mobile SEO: 98/100
Quick overview:
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn how to make pages mobile-friendly.
Tap targets are not sized appropriately
87% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), or have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more about tap targets.

Baseus.vn Mobile Best Practices: 33/100
Quick overview:
General
Issues were logged in the `Issues` panel in Chrome Devtools
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.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Uses third-party cookies
1 cookie found
Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.
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
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.
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
Baseus.vn Mobile PWA: 38/100
Quick overview:
PWA Optimized
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 about splash screens. Failures: No manifest was fetched.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more about theming the address bar. Failures: No manifest was fetched, The theme-color meta tag did not contain a content value.
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 about maskable manifest icons. 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 about manifest installability requirements.
Baseus.vn Mobile Accessibility: 65/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.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
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 about roles and required children elements.
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 about input field labels.
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 about heading order.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
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 how to make links 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.
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 about the viewport meta tag.
Similar tests
www.baseus.com
www.baseus.net
www.baseus.org
www.baseus.info
www.baseus.biz
www.baseus.us
www.baseus.mobi
www.aseus.vn
www.baseus.vn
www.vaseus.vn
www.bvaseus.vn
www.vbaseus.vn
www.gaseus.vn
www.bgaseus.vn
www.gbaseus.vn
www.haseus.vn
www.bhaseus.vn
www.hbaseus.vn
www.naseus.vn
www.bnaseus.vn
www.nbaseus.vn
www.bseus.vn
www.bqseus.vn
www.baqseus.vn
www.bqaseus.vn
www.bwseus.vn
www.bawseus.vn
www.bwaseus.vn
www.bsseus.vn
www.basseus.vn
www.bsaseus.vn
www.bzseus.vn
www.bazseus.vn
www.bzaseus.vn
www.baeus.vn
www.baweus.vn
www.basweus.vn
www.baeeus.vn
www.baseeus.vn
www.baeseus.vn
www.badeus.vn
www.basdeus.vn
www.badseus.vn
www.bazeus.vn
www.baszeus.vn
www.baxeus.vn
www.basxeus.vn
www.baxseus.vn
www.baaeus.vn
www.basaeus.vn
www.baaseus.vn
www.basus.vn
www.baswus.vn
www.basewus.vn
www.bassus.vn
www.basesus.vn
www.basdus.vn
www.basedus.vn
www.basrus.vn
www.baserus.vn
www.basreus.vn
www.bases.vn
www.baseys.vn
www.baseuys.vn
www.baseyus.vn
www.basehs.vn
www.baseuhs.vn
www.basehus.vn
www.basejs.vn
www.baseujs.vn
www.basejus.vn
www.baseis.vn
www.baseuis.vn
www.baseius.vn
www.baseu.vn
www.baseuw.vn
www.baseusw.vn
www.baseuws.vn
www.baseue.vn
www.baseuse.vn
www.baseues.vn
www.baseud.vn
www.baseusd.vn
www.baseuds.vn
www.baseuz.vn
www.baseusz.vn
www.baseuzs.vn
www.baseux.vn
www.baseusx.vn
www.baseuxs.vn
www.baseua.vn
www.baseusa.vn
www.baseuas.vn
Last Tested: