Blissos.org Site Title

Bliss OS

Blissos.org Meta Description

Open Source OS for PC's, based on AOSP

Blissos.org Test Results

Blissos.org Mobile Performance: 34/100
Quick overview:
Time to Interactive
19.7 s
Time to Interactive is the amount of time it takes for the page to become fully interactive. Learn more about the Time to Interactive metric.
Max Potential First Input Delay
630 ms
The maximum potential First Input Delay that your users could experience is the duration of the longest task. Learn more about the Maximum Potential First Input Delay metric.
First Meaningful Paint
3.8 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Network Requests
Lists the network requests that were made during page load.
Metrics
Collects all available metrics.
Server Backend Latencies
820 ms
Server latencies can impact web performance. If the server latency of an origin is high, it's an indication the server is overloaded or has poor backend performance. Learn more about server response time.
Network Round Trip Times
20 ms
Network round trip times (RTT) have a large impact on performance. If the RTT to an origin is high, it's an indication that servers closer to the user could improve performance. Learn more about the Round Trip Time.
Script Treemap Data
Used for treemap app
Final Screenshot
The last screenshot captured of the pageload.

1966966618188

Diagnostics
Collection of useful page vitals.
Tasks
Lists the toplevel main thread tasks that executed during page load.

Blissos.org 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 about the `alt` attribute.

Blissos.org Mobile Best Practices: 77/100
Quick overview:
General
Detected JavaScript libraries
All front-end JavaScript libraries detected on the page. Learn more about this JavaScript library detection diagnostic audit.
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 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 about HTTPS.
Ensure CSP is effective against XSS attacks
A strong Content Security Policy (CSP) significantly reduces the risk of cross-site scripting (XSS) attacks. Learn how to use a CSP to prevent XSS
Blissos.org Mobile PWA: 25/100
Quick overview:
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 how to size content for the viewport. The viewport size of 425px does not match the window size of 412px.
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 about maskable manifest icons. 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 about theming the address bar. 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 about splash screens. Failures: No manifest was fetched.
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 about manifest installability requirements.
Blissos.org Mobile Accessibility: 66/100
Quick overview:
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.
`[role]`s are not contained by their required parent element
Some ARIA child roles must be contained by specific parent roles to properly perform their intended accessibility functions. Learn more about ARIA roles and required parent element.
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 about roles and required children elements.
`[aria-*]` attributes do not match their roles
Each ARIA `role` supports a specific subset of `aria-*` attributes. Mismatching these invalidates the `aria-*` attributes. Learn how to match ARIA attributes to their roles.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
List items (`<li>`) are not contained within `<ul>`, `<ol>` or `<menu>` parent elements.
Screen readers require list items (`<li>`) to be contained within a parent `<ul>`, `<ol>` or `<menu>` to be announced properly. Learn more about proper list structure.
Identical links have the same purpose.
Links with the same destination should have the same description, to help users understand the link's purpose and decide whether to follow it. Learn more about identical links.
All heading elements contain content.
A heading with no content or inaccessible text prevent screen reader users from accessing information on the page's structure. Learn more about headings.
Document has a main landmark.
One main landmark helps screen reader users navigate a web page. Learn more about landmarks.
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 about frame titles.
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 how to make links accessible.
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 about the `alt` attribute.
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 about heading order.
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 how to provide sufficient color contrast.
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 about the `lang` attribute.
Similar tests
www.blissos.com
www.blissos.net
www.blissos.org
www.blissos.info
www.blissos.biz
www.blissos.us
www.blissos.mobi
www.lissos.org
www.blissos.org
www.vlissos.org
www.bvlissos.org
www.vblissos.org
www.glissos.org
www.bglissos.org
www.gblissos.org
www.hlissos.org
www.bhlissos.org
www.hblissos.org
www.nlissos.org
www.bnlissos.org
www.nblissos.org
www.bissos.org
www.bpissos.org
www.blpissos.org
www.bplissos.org
www.boissos.org
www.bloissos.org
www.bolissos.org
www.bkissos.org
www.blkissos.org
www.bklissos.org
www.blssos.org
www.blussos.org
www.bliussos.org
www.bluissos.org
www.bljssos.org
www.blijssos.org
www.bljissos.org
www.blkssos.org
www.blikssos.org
www.blossos.org
www.bliossos.org
www.blisos.org
www.bliwsos.org
www.bliswsos.org
www.bliwssos.org
www.bliesos.org
www.blisesos.org
www.bliessos.org
www.blidsos.org
www.blisdsos.org
www.blidssos.org
www.blizsos.org
www.bliszsos.org
www.blizssos.org
www.blixsos.org
www.blisxsos.org
www.blixssos.org
www.bliasos.org
www.blisasos.org
www.bliassos.org
www.bliswos.org
www.blisswos.org
www.bliseos.org
www.blisseos.org
www.blisdos.org
www.blissdos.org
www.bliszos.org
www.blisszos.org
www.blisxos.org
www.blissxos.org
www.blisaos.org
www.blissaos.org
www.blisss.org
www.blissis.org
www.blissois.org
www.blissios.org
www.blissks.org
www.blissoks.org
www.blisskos.org
www.blissls.org
www.blissols.org
www.blisslos.org
www.blissps.org
www.blissops.org
www.blisspos.org
www.blisso.org
www.blissow.org
www.blissosw.org
www.blissows.org
www.blissoe.org
www.blissose.org
www.blissoes.org
www.blissod.org
www.blissosd.org
www.blissods.org
www.blissoz.org
www.blissosz.org
www.blissozs.org
www.blissox.org
www.blissosx.org
www.blissoxs.org
www.blissoa.org
www.blissosa.org
www.blissoas.org
Last Tested: