Veriff.com Site Title

AI-powered Identity Verification Software – Veriff

Veriff.com Meta Description

Highly automated identity verification software from Veriff. We help you build trust and transparency online.

Veriff.com Test Results

Veriff.com Mobile Performance: 29/100
Quick overview:
Time to Interactive
24.7 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.
Max Potential First Input Delay
4,020 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Largest Contentful Paint element
21,630 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce the impact of third-party code
Third-party code blocked the main thread for 640 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 how to minimize third-party impact.
Avoid an excessive DOM size
2,817 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused JavaScript
Potential savings of 557 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
Reduce JavaScript execution time
22.4 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Minimize main-thread work
29.9 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn how to set image dimensions
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 about `font-display`.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 19 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 how to use modern JavaScript
Serve images in next-gen formats
Potential savings of 900 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Serve static assets with an efficient cache policy
2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Defer offscreen images
Potential savings of 1,335 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Avoid enormous network payloads
Total size was 4,376 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Properly size images
Potential savings of 195 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Efficiently encode images
Potential savings of 137 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.

Veriff.com Mobile SEO: 92/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Links do not have descriptive text
4 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Veriff.com Mobile Best Practices: 62/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 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.
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 third-party cookies
21 cookies found
Chrome is moving towards a new experience that allows users to choose to browse without third-party cookies. Learn more about third-party cookies.
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 about source maps.
Veriff.com Mobile Accessibility: 96/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.
Elements with `role="dialog"` or `role="alertdialog"` do not have accessible names.
ARIA dialog elements without accessible names may prevent screen readers users from discerning the purpose of these elements. Learn how to make ARIA dialog elements more accessible.
Similar sites
Similar tests
www.veriff.com
www.veriff.net
www.veriff.org
www.veriff.info
www.veriff.biz
www.veriff.us
www.veriff.mobi
www.eriff.com
www.veriff.com
www.ceriff.com
www.vceriff.com
www.cveriff.com
www.feriff.com
www.vferiff.com
www.fveriff.com
www.geriff.com
www.vgeriff.com
www.gveriff.com
www.beriff.com
www.vberiff.com
www.bveriff.com
www.vriff.com
www.vwriff.com
www.vewriff.com
www.vweriff.com
www.vsriff.com
www.vesriff.com
www.vseriff.com
www.vdriff.com
www.vedriff.com
www.vderiff.com
www.vrriff.com
www.verriff.com
www.vreriff.com
www.veiff.com
www.veeiff.com
www.vereiff.com
www.veeriff.com
www.vediff.com
www.verdiff.com
www.vefiff.com
www.verfiff.com
www.vefriff.com
www.vetiff.com
www.vertiff.com
www.vetriff.com
www.verff.com
www.veruff.com
www.veriuff.com
www.veruiff.com
www.verjff.com
www.verijff.com
www.verjiff.com
www.verkff.com
www.verikff.com
www.verkiff.com
www.veroff.com
www.verioff.com
www.veroiff.com
www.verif.com
www.vericf.com
www.verifcf.com
www.vericff.com
www.veridf.com
www.verifdf.com
www.veridff.com
www.verirf.com
www.verifrf.com
www.verirff.com
www.veritf.com
www.veriftf.com
www.veritff.com
www.verigf.com
www.verifgf.com
www.verigff.com
www.verivf.com
www.verifvf.com
www.verivff.com
www.verifc.com
www.veriffc.com
www.verifd.com
www.veriffd.com
www.verifr.com
www.veriffr.com
www.verift.com
www.verifft.com
www.verifg.com
www.veriffg.com
www.verifv.com
www.veriffv.com
www.veriff.con
Last Tested: