Isigner.app Site Title

iSigner

Isigner.app Test Results

Isigner.app Mobile Performance: 39/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 270 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Reduce initial server response time. Root document took 1,030 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Avoid serving legacy JavaScript to modern browsers. Potential savings of 18 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 More
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Serve static assets with an efficient cache policy
12 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
2.5 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
1.5 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Avoid long main-thread tasks
9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
1 chain 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
16 requests • 541 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Isigner.app Mobile SEO: 92/100
Quick overview:
Crawling and Indexing
To appear in search results, crawlers need access to your app.
robots.txt is not valid
159 errors found
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.

Isigner.app Mobile Best Practices: 86/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.
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.
General
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.
Isigner.app Mobile Progressive Web App: 46/100
Quick overview:
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, No `<meta name="theme-color">` tag found.
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.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
Installable
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.
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.
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.
`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.
Isigner.app Mobile Accessibility: 82/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.
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.
Navigation
These are opportunities to improve keyboard navigation in your application.
The page does not contain a heading, skip link, or landmark region
Adding ways to bypass repetitive content lets keyboard users navigate the page more efficiently. 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 tests
www.isigner.com
www.isigner.net
www.isigner.org
www.isigner.info
www.isigner.biz
www.isigner.us
www.isigner.mobi
www.signer.app
www.isigner.app
www.usigner.app
www.iusigner.app
www.uisigner.app
www.jsigner.app
www.ijsigner.app
www.jisigner.app
www.ksigner.app
www.iksigner.app
www.kisigner.app
www.osigner.app
www.iosigner.app
www.oisigner.app
www.iigner.app
www.iwigner.app
www.iswigner.app
www.iwsigner.app
www.ieigner.app
www.iseigner.app
www.iesigner.app
www.idigner.app
www.isdigner.app
www.idsigner.app
www.izigner.app
www.iszigner.app
www.izsigner.app
www.ixigner.app
www.isxigner.app
www.ixsigner.app
www.iaigner.app
www.isaigner.app
www.iasigner.app
www.isgner.app
www.isugner.app
www.isiugner.app
www.isuigner.app
www.isjgner.app
www.isijgner.app
www.isjigner.app
www.iskgner.app
www.isikgner.app
www.iskigner.app
www.isogner.app
www.isiogner.app
www.isoigner.app
www.isiner.app
www.isifner.app
www.isigfner.app
www.isifgner.app
www.isivner.app
www.isigvner.app
www.isivgner.app
www.isitner.app
www.isigtner.app
www.isitgner.app
www.isibner.app
www.isigbner.app
www.isibgner.app
www.isiyner.app
www.isigyner.app
www.isiygner.app
www.isihner.app
www.isighner.app
www.isihgner.app
www.isiger.app
www.isigber.app
www.isignber.app
www.isigher.app
www.isignher.app
www.isigjer.app
www.isignjer.app
www.isigjner.app
www.isigmer.app
www.isignmer.app
www.isigmner.app
www.isignr.app
www.isignwr.app
www.isignewr.app
www.isignwer.app
www.isignsr.app
www.isignesr.app
www.isignser.app
www.isigndr.app
www.isignedr.app
www.isignder.app
www.isignrr.app
www.isignerr.app
www.isignrer.app
www.isigne.app
www.isignee.app
www.isignere.app
www.isigneer.app
www.isigned.app
www.isignerd.app
www.isignef.app
www.isignerf.app
www.isignefr.app
www.isignet.app
www.isignert.app
www.isignetr.app
Last Tested: