101face.ru Site Title

Marvel Superhero Marvel counts among its characters...

101face.ru Meta Description

marvel superhero Birthday Fun w/ Spidey, Black Panther & Shuri! | Marvel Super Hero Adventures | Obstacle, Of Course. Marvel HQ. 101face.ru

101face.ru Test Results

101face.ru Mobile Performance: 57/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 18,375 KB
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
Properly size images. Potential savings of 6,045 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Serve images in next-gen formats. Potential savings of 984 KB
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.
Efficiently encode images. Potential savings of 308 KB
Optimized images load faster and consume less cellular data. Learn more.
Reduce initial server response time. Root document took 940 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Remove unused JavaScript. Potential savings of 31 KB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Enable text compression. Potential savings of 16 KB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Eliminate render-blocking resources. Potential savings of 120 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Avoid enormous network payloads
Total size was 25,336 KB
Large network payloads cost users real money and are highly correlated with long load times. Learn more.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn more.
Serve static assets with an efficient cache policy
54 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
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.
Minimize main-thread work
2.2 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Avoid chaining critical requests
11 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
61 requests • 25,336 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
5 elements found
These DOM elements contribute most to the CLS of the page.
Largest Contentful Paint element
1 element found
This is the element that was identified as the Largest Contentful Paint. Learn More

101face.ru 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.
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.

101face.ru Mobile Best Practices: 54/100
Quick overview:
User Experience
Displays images with inappropriate size
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn more.
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more.
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.
Includes front-end JavaScript libraries with known security vulnerabilities
4 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. 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
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
101face.ru Mobile Progressive Web App: 46/100
Quick overview:
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.
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
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.
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.
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. This page is controlled by a service worker, however no `start_url` was found because no manifest was fetched.
101face.ru Mobile Accessibility: 61/100
Quick overview:
Navigation
These are opportunities to improve keyboard navigation in your application.
Heading elements are not in a sequentially-descending order
Properly ordered headings that do not skip levels convey the semantic structure of the page, making it easier to navigate and understand when using assistive technologies. 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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
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 more.
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.
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 sites
Similar tests
www.101face.com
www.101face.net
www.101face.org
www.101face.info
www.101face.biz
www.101face.us
www.101face.mobi
www.01face.ru
www.101face.ru
www.11face.ru
www.10face.ru
www.101ace.ru
www.101cace.ru
www.101fcace.ru
www.101cface.ru
www.101dace.ru
www.101fdace.ru
www.101dface.ru
www.101race.ru
www.101frace.ru
www.101rface.ru
www.101tace.ru
www.101ftace.ru
www.101tface.ru
www.101gace.ru
www.101fgace.ru
www.101gface.ru
www.101vace.ru
www.101fvace.ru
www.101vface.ru
www.101fce.ru
www.101fqce.ru
www.101faqce.ru
www.101fqace.ru
www.101fwce.ru
www.101fawce.ru
www.101fwace.ru
www.101fsce.ru
www.101fasce.ru
www.101fsace.ru
www.101fzce.ru
www.101fazce.ru
www.101fzace.ru
www.101fae.ru
www.101faxe.ru
www.101facxe.ru
www.101faxce.ru
www.101fade.ru
www.101facde.ru
www.101fadce.ru
www.101fafe.ru
www.101facfe.ru
www.101fafce.ru
www.101fave.ru
www.101facve.ru
www.101favce.ru
www.101fac.ru
www.101facw.ru
www.101facew.ru
www.101facwe.ru
www.101facs.ru
www.101faces.ru
www.101facse.ru
www.101facd.ru
www.101faced.ru
www.101facr.ru
www.101facer.ru
www.101facre.ru
Last Tested: