Donic.com Site Title

CREATE SUCCESS

Donic.com Test Results

Donic.com Mobile Performance: 18/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 567 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Preload key requests. Potential savings of 3,480 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Serve images in next-gen formats. Potential savings of 516 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Remove unused CSS. Potential savings of 139 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Avoid multiple page redirects. Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Properly size images. Potential savings of 170 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Minify JavaScript. Potential savings of 113 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Eliminate render-blocking resources. Potential savings of 490 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.
Reduce initial server response time. Root document took 980 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,410 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.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. 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.
Minimize main-thread work
7.7 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
11 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
3.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid an excessive DOM size
857 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn more.
Avoids enormous network payloads
Total size was 2,572 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid chaining critical requests
11 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 long main-thread tasks
16 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
74 requests • 2,572 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
User Timing marks and measures
4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.

Donic.com Mobile SEO: 77/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
If your robots.txt file is malformed, crawlers may not be able to understand how you want your website to be crawled or indexed. Learn more. Lighthouse was unable to download a robots.txt file
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more. Description text is empty.
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.
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 more.
Tap targets are not sized appropriately
94% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Donic.com Mobile Best Practices: 69/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.
Includes front-end JavaScript libraries with known security vulnerabilities
3 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
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 more.
General
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
Donic.com Mobile Progressive Web App: 25/100
Quick overview:
PWA Optimized
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.
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
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.
Fast and reliable
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 14.4 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.
`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. No usable web app manifest found on page.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
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.
Donic.com Mobile Accessibility: 56/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.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. 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.
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.
`[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.
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.
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 sites
Similar tests
www.donic.com
www.donic.net
www.donic.org
www.donic.info
www.donic.biz
www.donic.us
www.donic.mobi
www.onic.com
www.donic.com
www.xonic.com
www.dxonic.com
www.xdonic.com
www.sonic.com
www.dsonic.com
www.sdonic.com
www.eonic.com
www.deonic.com
www.edonic.com
www.ronic.com
www.dronic.com
www.rdonic.com
www.fonic.com
www.dfonic.com
www.fdonic.com
www.conic.com
www.dconic.com
www.cdonic.com
www.dnic.com
www.dinic.com
www.doinic.com
www.dionic.com
www.dknic.com
www.doknic.com
www.dkonic.com
www.dlnic.com
www.dolnic.com
www.dlonic.com
www.dpnic.com
www.dopnic.com
www.dponic.com
www.doic.com
www.dobic.com
www.donbic.com
www.dobnic.com
www.dohic.com
www.donhic.com
www.dohnic.com
www.dojic.com
www.donjic.com
www.dojnic.com
www.domic.com
www.donmic.com
www.domnic.com
www.donc.com
www.donuc.com
www.doniuc.com
www.donuic.com
www.donjc.com
www.donijc.com
www.donkc.com
www.donikc.com
www.donkic.com
www.donoc.com
www.donioc.com
www.donoic.com
www.doni.com
www.donix.com
www.donicx.com
www.donixc.com
www.donid.com
www.donicd.com
www.donidc.com
www.donif.com
www.donicf.com
www.donifc.com
www.doniv.com
www.donicv.com
www.donivc.com
www.donic.con
Last Tested: