Billdu.com Site Title

Billdu: Invoicing Software for Small Businesses

Billdu.com Meta Description

Professional invoicing software for small businesses. Create professional-looking invoices, estimates, purchase orders, delivery notes, & more with Billdu app

Billdu.com Test Results

Billdu.com Mobile Performance: 8/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Use video formats for animated content. Potential savings of 1,019 KiB
Large GIFs are inefficient for delivering animated content. Consider using MPEG4/WebM videos for animations and PNG/WebP for static images instead of GIF to save network bytes. Learn more
Eliminate render-blocking resources. Potential savings of 4,480 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.
Defer offscreen images. Potential savings of 1,974 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Remove unused JavaScript. Potential savings of 441 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid multiple page redirects. Potential savings of 1,260 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Remove unused CSS. Potential savings of 204 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.
Serve images in next-gen formats. Potential savings of 178 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 290 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.
Minimize main-thread work
9.8 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
6.0 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
5 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid an excessive DOM size
1,180 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 3,253 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
50 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.
Keep request counts low and transfer sizes small
90 requests • 3,253 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
Avoid long main-thread tasks
17 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more

Billdu.com Mobile SEO: 93/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.

Billdu.com Mobile Best Practices: 62/100
Quick overview:
Trust and Safety
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.
Does not use HTTPS
2 insecure requests 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
5 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. 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
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.
Billdu.com Mobile Progressive Web App: 25/100
Quick overview:
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.
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 use HTTPS
2 insecure requests 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.
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. No usable web app manifest found on page.
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 16.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.
PWA Optimized
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 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.
Billdu.com Mobile Accessibility: 63/100
Quick overview:
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.
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 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.
`[aria-*]` attributes do not have valid values
Assistive technologies, like screen readers, can't interpret ARIA attributes with invalid values. Learn more.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn more.
Tables and lists
These are opportunities to to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>` or `<ol>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>` or `<ol>` to be announced properly. 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.
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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. 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.
Similar sites
Similar tests
www.billdu.com
www.billdu.net
www.billdu.org
www.billdu.info
www.billdu.biz
www.billdu.us
www.billdu.mobi
www.illdu.com
www.billdu.com
www.villdu.com
www.bvilldu.com
www.vbilldu.com
www.gilldu.com
www.bgilldu.com
www.gbilldu.com
www.hilldu.com
www.bhilldu.com
www.hbilldu.com
www.nilldu.com
www.bnilldu.com
www.nbilldu.com
www.blldu.com
www.bulldu.com
www.biulldu.com
www.builldu.com
www.bjlldu.com
www.bijlldu.com
www.bjilldu.com
www.bklldu.com
www.biklldu.com
www.bkilldu.com
www.bolldu.com
www.biolldu.com
www.boilldu.com
www.bildu.com
www.bipldu.com
www.bilpldu.com
www.biplldu.com
www.bioldu.com
www.biloldu.com
www.bikldu.com
www.bilkldu.com
www.bilpdu.com
www.billpdu.com
www.bilodu.com
www.billodu.com
www.bilkdu.com
www.billkdu.com
www.billu.com
www.billxu.com
www.billdxu.com
www.billxdu.com
www.billsu.com
www.billdsu.com
www.billsdu.com
www.billeu.com
www.billdeu.com
www.billedu.com
www.billru.com
www.billdru.com
www.billrdu.com
www.billfu.com
www.billdfu.com
www.billfdu.com
www.billcu.com
www.billdcu.com
www.billcdu.com
www.billd.com
www.billdy.com
www.billduy.com
www.billdyu.com
www.billdh.com
www.billduh.com
www.billdhu.com
www.billdj.com
www.billduj.com
www.billdju.com
www.billdi.com
www.billdui.com
www.billdiu.com
www.billdu.con
Last Tested: