Respeak.net Site Title

Respeak

Respeak.net Meta Description

Respeak.net is a global social networking platform meant to be the social network we deserve. Say something worth sharing.

Respeak.net Test Results

Respeak.net Mobile Performance: 74/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 1,510 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 CSS. Potential savings of 51 KB
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 62 KB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Defer offscreen images. Potential savings of 39 KB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn more.
Serve images in next-gen formats. Potential savings of 35 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.
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.
Serve static assets with an efficient cache policy
20 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Avoid chaining critical requests
16 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
31 requests • 629 KB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Respeak.net Mobile SEO: 70/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
1 link found
Descriptive link text helps search engines understand your content. Learn more.
Document does not have a valid `rel=canonical`
Canonical links suggest which URL to show in search results. Learn more. Relative URL (https:)
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.
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
16% 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.

Respeak.net Mobile Best Practices: 69/100
Quick overview:
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.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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
6 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Respeak.net Mobile Progressive Web App: 41/100
Quick overview:
PWA Optimized
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.
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.
Installable
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. 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.
Respeak.net Mobile Accessibility: 73/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.
Best practices
These items highlight common accessibility best practices.
`[id]` attributes on the page are not unique
The value of an id attribute must be unique to prevent other instances from being overlooked by assistive technologies. Learn more.
`[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.
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.
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.
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 an ARIA `[role]` that require children to contain a specific `[role]` are missing some or all of those required children.
Some ARIA parent roles must contain specific child roles to perform their intended accessibility functions. Learn more.
Similar tests
www.respeak.com
www.respeak.net
www.respeak.org
www.respeak.info
www.respeak.biz
www.respeak.us
www.respeak.mobi
www.espeak.net
www.respeak.net
www.eespeak.net
www.reespeak.net
www.erespeak.net
www.despeak.net
www.rdespeak.net
www.drespeak.net
www.fespeak.net
www.rfespeak.net
www.frespeak.net
www.tespeak.net
www.rtespeak.net
www.trespeak.net
www.rspeak.net
www.rwspeak.net
www.rewspeak.net
www.rwespeak.net
www.rsspeak.net
www.resspeak.net
www.rsespeak.net
www.rdspeak.net
www.redspeak.net
www.rrspeak.net
www.rerspeak.net
www.rrespeak.net
www.repeak.net
www.rewpeak.net
www.reswpeak.net
www.reepeak.net
www.resepeak.net
www.redpeak.net
www.resdpeak.net
www.rezpeak.net
www.reszpeak.net
www.rezspeak.net
www.rexpeak.net
www.resxpeak.net
www.rexspeak.net
www.reapeak.net
www.resapeak.net
www.reaspeak.net
www.reseak.net
www.resoeak.net
www.respoeak.net
www.resopeak.net
www.resleak.net
www.respleak.net
www.reslpeak.net
www.respak.net
www.respwak.net
www.respewak.net
www.respweak.net
www.respsak.net
www.respesak.net
www.respseak.net
www.respdak.net
www.respedak.net
www.respdeak.net
www.resprak.net
www.resperak.net
www.respreak.net
www.respek.net
www.respeqk.net
www.respeaqk.net
www.respeqak.net
www.respewk.net
www.respeawk.net
www.respesk.net
www.respeask.net
www.respezk.net
www.respeazk.net
www.respezak.net
www.respea.net
www.respeaj.net
www.respeakj.net
www.respeajk.net
www.respeai.net
www.respeaki.net
www.respeaik.net
www.respeam.net
www.respeakm.net
www.respeamk.net
www.respeal.net
www.respeakl.net
www.respealk.net
www.respeao.net
www.respeako.net
www.respeaok.net
Last Tested: