Why-people.com Site Title

Why People

Why-people.com Meta Description

Why-People is a Social Networking Platform. With our new feature, user can wonder posts, photos,

Why-people.com Test Results

Why-people.com Mobile Performance: 20/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 2,230 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.
Remove unused JavaScript. Potential savings of 230 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Remove unused CSS. Potential savings of 50 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Properly size images. Potential savings of 120 KiB
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 75 KiB
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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,120 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 more.
Serve static assets with an efficient cache policy
29 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
6.3 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
4.4 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.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid long main-thread tasks
20 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
51 requests • 796 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
1 element found
These DOM elements contribute most to the CLS of the page.

Why-people.com Mobile SEO: 81/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.
Links do not have descriptive text
1 link found
Descriptive link text helps search engines understand your content. 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.
Tap targets are not sized appropriately
64% appropriately sized tap targets
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.

Why-people.com Mobile Best Practices: 57/100
Quick overview:
General
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more.
Registers an `unload` listener
The `unload` event does not fire reliably and listening for it can prevent browser optimizations like the Back-Forward Cache. Consider using the `pagehide` or `visibilitychange` events instead. Learn More
Trust and Safety
Includes front-end JavaScript libraries with known security vulnerabilities
8 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Requests the notification permission on page load
Users are mistrustful of or confused by sites that request to send notifications without context. Consider tying the request to user gestures instead. 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.
Does not use HTTPS
7 insecure requests 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.
Why-people.com Mobile Progressive Web App: 39/100
Quick overview:
PWA Optimized
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 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.
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.
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 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.
Installable
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.
Does not use HTTPS
7 insecure requests 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.
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.
Why-people.com Mobile Accessibility: 84/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.
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.
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.
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.
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.
Similar sites
Similar tests
www.why-people.com
www.why-people.net
www.why-people.org
www.why-people.info
www.why-people.biz
www.why-people.us
www.why-people.mobi
www.hy-people.com
www.why-people.com
www.qhy-people.com
www.wqhy-people.com
www.qwhy-people.com
www.ahy-people.com
www.wahy-people.com
www.awhy-people.com
www.shy-people.com
www.wshy-people.com
www.swhy-people.com
www.ehy-people.com
www.wehy-people.com
www.ewhy-people.com
www.wy-people.com
www.wby-people.com
www.whby-people.com
www.wbhy-people.com
www.wgy-people.com
www.whgy-people.com
www.wghy-people.com
www.wyy-people.com
www.whyy-people.com
www.wyhy-people.com
www.wuy-people.com
www.whuy-people.com
www.wuhy-people.com
www.wjy-people.com
www.whjy-people.com
www.wjhy-people.com
www.wny-people.com
www.whny-people.com
www.wnhy-people.com
www.wh-people.com
www.wht-people.com
www.whyt-people.com
www.whty-people.com
www.whg-people.com
www.whyg-people.com
www.whh-people.com
www.whyh-people.com
www.whhy-people.com
www.whu-people.com
www.whyu-people.com
www.whypeople.com
www.why-eople.com
www.why-oeople.com
www.why-poeople.com
www.why-opeople.com
www.why-leople.com
www.why-pleople.com
www.why-lpeople.com
www.why-pople.com
www.why-pwople.com
www.why-pewople.com
www.why-pweople.com
www.why-psople.com
www.why-pesople.com
www.why-pseople.com
www.why-pdople.com
www.why-pedople.com
www.why-pdeople.com
www.why-prople.com
www.why-perople.com
www.why-preople.com
www.why-peple.com
www.why-peiple.com
www.why-peoiple.com
www.why-peiople.com
www.why-pekple.com
www.why-peokple.com
www.why-pekople.com
www.why-pelple.com
www.why-peolple.com
www.why-pelople.com
www.why-pepple.com
www.why-peopple.com
www.why-pepople.com
www.why-peole.com
www.why-peoole.com
www.why-peopole.com
www.why-peoople.com
www.why-peolle.com
www.why-peoplle.com
www.why-peope.com
www.why-peoppe.com
www.why-peoplpe.com
www.why-peopoe.com
www.why-peoploe.com
www.why-peopke.com
www.why-peoplke.com
www.why-peopkle.com
www.why-peopl.com
www.why-peoplw.com
www.why-peoplew.com
www.why-peoplwe.com
www.why-peopls.com
www.why-peoples.com
www.why-peoplse.com
www.why-peopld.com
www.why-peopled.com
www.why-peoplde.com
www.why-peoplr.com
www.why-peopler.com
www.why-peoplre.com
www.why-people.con
Last Tested: