Biddr.com Site Title

biddr - the modern auction platform for numismatic items

Biddr.com Meta Description

Bid on ancient coins, world coins, medals, banknotes and antiquities and take part in numerous numismatic auctions worldwide.

Biddr.com Test Results

Biddr.com Mobile Performance: 69/100
Quick overview:
Max Potential First Input Delay
290 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.
First Meaningful Paint
2.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Time to Interactive
4.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.
Server Backend Latencies
80 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Resources Summary
Aggregates all network requests and groups them by type
Network Round Trip Times
40 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Network Requests
Lists the network requests that were made during page load.
Diagnostics
Collection of useful page vitals.
Final Screenshot
The last screenshot captured of the pageload.

824141899672

Metrics
Collects all available metrics.
Tasks
Lists the toplevel main thread tasks that executed during page load.
Script Treemap Data
Used for treemap app

Biddr.com 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
76% 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.

Biddr.com Mobile Best Practices: 78/100
Quick overview:
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
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.
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.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Biddr.com Mobile PWA: 88/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 about theming the address bar. Failures: No `<meta name="theme-color">` tag found.
Biddr.com Mobile Accessibility: 66/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 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.
Values assigned to `role=""` are not valid ARIA roles.
ARIA `role`s enable assistive technologies to know the role of each element on the web page. If the `role` values are misspelled, not existing ARIA `role` values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA 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.
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.
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.
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 how to make buttons more accessible.
Select elements do not have associated label elements.
Form elements without effective labels can create frustrating experiences for screen reader users. Learn more about the `select` element.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
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 sites
Similar tests
www.biddr.com
www.biddr.net
www.biddr.org
www.biddr.info
www.biddr.biz
www.biddr.us
www.biddr.mobi
www.iddr.com
www.biddr.com
www.viddr.com
www.bviddr.com
www.vbiddr.com
www.giddr.com
www.bgiddr.com
www.gbiddr.com
www.hiddr.com
www.bhiddr.com
www.hbiddr.com
www.niddr.com
www.bniddr.com
www.nbiddr.com
www.bddr.com
www.buddr.com
www.biuddr.com
www.buiddr.com
www.bjddr.com
www.bijddr.com
www.bjiddr.com
www.bkddr.com
www.bikddr.com
www.bkiddr.com
www.boddr.com
www.bioddr.com
www.boiddr.com
www.bidr.com
www.bixdr.com
www.bidxdr.com
www.bixddr.com
www.bisdr.com
www.bidsdr.com
www.bisddr.com
www.biedr.com
www.bidedr.com
www.bieddr.com
www.birdr.com
www.bidrdr.com
www.birddr.com
www.bifdr.com
www.bidfdr.com
www.bifddr.com
www.bicdr.com
www.bidcdr.com
www.bicddr.com
www.bidxr.com
www.biddxr.com
www.bidsr.com
www.biddsr.com
www.bider.com
www.bidder.com
www.bidrr.com
www.biddrr.com
www.bidfr.com
www.biddfr.com
www.bidcr.com
www.biddcr.com
www.bidd.com
www.bidde.com
www.biddre.com
www.biddd.com
www.biddrd.com
www.bidddr.com
www.biddf.com
www.biddrf.com
www.biddt.com
www.biddrt.com
www.biddtr.com
www.biddr.con
Last Tested: