Xfact.net Test Results

Xfact.net Mobile Performance: 97/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Reduce initial server response time. Root document took 2,720 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.
Avoid long main-thread tasks
1 long task 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
Keep request counts low and transfer sizes small
1 request • 0 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Xfact.net Mobile SEO: 55/100
Quick overview:
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.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. 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.
Document doesn't use legible font sizes
Font sizes less than 12px are too small to be legible and require mobile visitors to “pinch to zoom” in order to read. Strive to have >60% of page text ≥12px. Learn more. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
Tap targets are not sized appropriately
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. Tap targets are too small because there's no viewport meta tag optimized for mobile screens

Xfact.net 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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more. Document must contain a doctype
Xfact.net Mobile Progressive Web App: 29/100
Quick overview:
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.
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.
PWA Optimized
Content is not sized correctly for the viewport
If the width of your app's content doesn't match the width of the viewport, your app might not be optimized for mobile screens. Learn more. The viewport size of 980px does not match the window size of 360px.
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.
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 have a `<meta name="viewport">` tag with `width` or `initial-scale`
Add a `<meta name="viewport">` tag to optimize your app for mobile screens. Learn more. No `<meta name="viewport">` tag found
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.
Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. 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.
Xfact.net Mobile Accessibility: 68/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.
Document doesn't have a `<title>` element
The title gives screen reader users an overview of the page, and search engine users rely on it heavily to determine if a page is relevant to their search. Learn more.
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
`<html>` element does not have a `[lang]` attribute
If a page doesn't specify a lang attribute, a screen reader assumes that the page is in the default language that the user chose when setting up the screen reader. If the page isn't actually in the default language, then the screen reader might not announce the page's text correctly. Learn more.
Similar tests
www.xfact.com
www.xfact.net
www.xfact.org
www.xfact.info
www.xfact.biz
www.xfact.us
www.xfact.mobi
www.fact.net
www.xfact.net
www.zfact.net
www.xzfact.net
www.zxfact.net
www.sfact.net
www.xsfact.net
www.sxfact.net
www.dfact.net
www.xdfact.net
www.dxfact.net
www.cfact.net
www.xcfact.net
www.cxfact.net
www.xact.net
www.xcact.net
www.xfcact.net
www.xdact.net
www.xfdact.net
www.xract.net
www.xfract.net
www.xrfact.net
www.xtact.net
www.xftact.net
www.xtfact.net
www.xgact.net
www.xfgact.net
www.xgfact.net
www.xvact.net
www.xfvact.net
www.xvfact.net
www.xfct.net
www.xfqct.net
www.xfaqct.net
www.xfqact.net
www.xfwct.net
www.xfawct.net
www.xfwact.net
www.xfsct.net
www.xfasct.net
www.xfsact.net
www.xfzct.net
www.xfazct.net
www.xfzact.net
www.xfat.net
www.xfaxt.net
www.xfacxt.net
www.xfaxct.net
www.xfadt.net
www.xfacdt.net
www.xfadct.net
www.xfaft.net
www.xfacft.net
www.xfafct.net
www.xfavt.net
www.xfacvt.net
www.xfavct.net
www.xfac.net
www.xfacr.net
www.xfactr.net
www.xfacrt.net
www.xfacf.net
www.xfactf.net
www.xfacg.net
www.xfactg.net
www.xfacgt.net
www.xfacy.net
www.xfacty.net
www.xfacyt.net
Last Tested:

This website uses cookies to ensure you get the best experience on our website. Learn more. Got it.