Splasho.com Test Results

Splasho.com Mobile Performance: 49/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 511 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Avoid multiple page redirects. Potential savings of 1,290 ms
Redirects introduce additional delays before the page can be loaded. Learn more.
Reduce initial server response time. Root document took 1,130 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Remove unused CSS. Potential savings of 89 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.
Eliminate render-blocking resources. Potential savings of 600 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.
Serve images in next-gen formats. Potential savings of 90 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.
Efficiently encode images. Potential savings of 60 KiB
Optimized images load faster and consume less cellular data. Learn more.
Use HTTP/2. 6 requests not served via HTTP/2
HTTP/2 offers many benefits over HTTP/1.1, including binary headers and multiplexing. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Image elements do not have explicit `width` and `height`
Set an explicit width and height on image elements to reduce layout shifts and improve CLS. Learn more
Does not use passive listeners to improve scrolling performance
Consider marking your touch and wheel event listeners as `passive` to improve your page's scroll performance. Learn more.
Some third-party resources can be lazy loaded with a facade
1 facade alternative available
Some third-party embeds can be lazy loaded. Consider replacing them with a facade until they are required. Learn more.
Reduce the impact of third-party code
Third-party code blocked the main thread for 860 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.
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
12 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
2.9 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.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
User Timing marks and measures
4 user timings
Consider instrumenting your app with the User Timing API to measure your app's real-world performance during key user experiences. Learn more.
Keep request counts low and transfer sizes small
43 requests • 1,156 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid large layout shifts
2 elements found
These DOM elements contribute most to the CLS of the page.
Avoid chaining critical requests
13 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.
Avoid long main-thread tasks
8 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

Splasho.com Mobile SEO: 69/100
Quick overview:
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
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
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
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.

Splasho.com Mobile Best Practices: 60/100
Quick overview:
Trust and Safety
Does not use HTTPS
3 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 served over 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.
General
Issues were logged in the `Issues` panel in Chrome Devtools
Issues logged to the `Issues` panel in Chrome Devtools indicate unresolved problems. They can come from network request failures, insufficient security controls, and other browser concerns. Open up the Issues panel in Chrome DevTools for more details on each issue.
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
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. 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
Splasho.com Mobile Progressive Web App: 25/100
Quick overview:
Installable
Web app manifest or service worker do not meet the installability requirements
1 reason
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. With proper service worker and manifest implementations, browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more.
PWA Optimized
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.
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 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.
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.
Splasho.com Mobile Accessibility: 95/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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Similar sites
Similar tests
www.splasho.com
www.splasho.net
www.splasho.org
www.splasho.info
www.splasho.biz
www.splasho.us
www.splasho.mobi
www.plasho.com
www.splasho.com
www.wplasho.com
www.swplasho.com
www.wsplasho.com
www.eplasho.com
www.seplasho.com
www.esplasho.com
www.dplasho.com
www.sdplasho.com
www.dsplasho.com
www.zplasho.com
www.szplasho.com
www.zsplasho.com
www.xplasho.com
www.sxplasho.com
www.xsplasho.com
www.aplasho.com
www.saplasho.com
www.asplasho.com
www.slasho.com
www.solasho.com
www.spolasho.com
www.soplasho.com
www.sllasho.com
www.spllasho.com
www.slplasho.com
www.spasho.com
www.sppasho.com
www.splpasho.com
www.spplasho.com
www.spoasho.com
www.sploasho.com
www.spkasho.com
www.splkasho.com
www.spklasho.com
www.splsho.com
www.splqsho.com
www.splaqsho.com
www.splqasho.com
www.splwsho.com
www.splawsho.com
www.splwasho.com
www.splssho.com
www.splassho.com
www.splsasho.com
www.splzsho.com
www.splazsho.com
www.splzasho.com
www.splaho.com
www.splawho.com
www.splaswho.com
www.splaeho.com
www.splaseho.com
www.splaesho.com
www.spladho.com
www.splasdho.com
www.spladsho.com
www.splazho.com
www.splaszho.com
www.splaxho.com
www.splasxho.com
www.splaxsho.com
www.splaaho.com
www.splasaho.com
www.splaasho.com
www.splaso.com
www.splasbo.com
www.splashbo.com
www.splasbho.com
www.splasgo.com
www.splashgo.com
www.splasgho.com
www.splasyo.com
www.splashyo.com
www.splasyho.com
www.splasuo.com
www.splashuo.com
www.splasuho.com
www.splasjo.com
www.splashjo.com
www.splasjho.com
www.splasno.com
www.splashno.com
www.splasnho.com
www.splash.com
www.splashi.com
www.splashoi.com
www.splashio.com
www.splashk.com
www.splashok.com
www.splashko.com
www.splashl.com
www.splashol.com
www.splashlo.com
www.splashp.com
www.splashop.com
www.splashpo.com
www.splasho.con
Last Tested: