Intbau.org Test Results

Intbau.org Mobile Performance: 50/100
Quick overview:
Time to Interactive
5.4 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.
First Meaningful Paint
3.1 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused CSS
Potential savings of 14 KiB
Reduce unused rules from stylesheets and defer CSS not used for above-the-fold content to decrease bytes consumed by network activity. Learn how to reduce unused CSS.
Avoid large layout shifts
3 layout shifts found
These are the largest layout shifts observed on the page. Each table item represents a single layout shift, and shows the element that shifted the most. Below each item are possible root causes that led to the layout shift. Some of these layout shifts may not be included in the CLS metric value due to windowing. Learn how to improve CLS
Properly size images
Potential savings of 1,170 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
9,080 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid multiple page redirects
Potential savings of 1,260 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Efficiently encode images
Potential savings of 298 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Eliminate render-blocking resources
Potential savings of 1,240 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn how to eliminate render-blocking resources.
Serve images in next-gen formats
Potential savings of 4,166 KiB
Image formats like WebP and AVIF often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more about modern image formats.
Reduce unused JavaScript
Potential savings of 44 KiB
Reduce unused JavaScript and defer loading scripts until they are required to decrease bytes consumed by network activity. Learn how to reduce unused JavaScript.
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 about `font-display`.
Serve static assets with an efficient cache policy
43 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Minify JavaScript
Potential savings of 5 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn how to minify JavaScript.
Minify CSS
Potential savings of 4 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Avoid enormous network payloads
Total size was 26,521 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.

Intbau.org Mobile SEO: 83/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.
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Links are not crawlable
Search engines may use `href` attributes on links to crawl websites. Ensure that the `href` attribute of anchor elements links to an appropriate destination, so more pages of the site can be discovered. Learn how to make links crawlable

Intbau.org Mobile Best Practices: 83/100
Quick overview:
Trust and Safety
Does not use HTTPS
2 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 about HTTPS.
Intbau.org Mobile Accessibility: 74/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.
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.
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Lists do not contain only `<li>` elements and script supporting elements (`<script>` and `<template>`).
Screen readers have a specific way of announcing lists. Ensuring proper list structure aids screen reader output. Learn more about proper list structure.
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.
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 use prohibited ARIA attributes
Using ARIA attributes in roles where they are prohibited can mean that important information is not communicated to users of assistive technologies. Learn more about prohibited ARIA roles.
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 about the viewport meta tag.
Similar tests
www.intbau.com
www.intbau.net
www.intbau.org
www.intbau.info
www.intbau.biz
www.intbau.us
www.intbau.mobi
www.ntbau.org
www.intbau.org
www.untbau.org
www.iuntbau.org
www.uintbau.org
www.jntbau.org
www.ijntbau.org
www.jintbau.org
www.kntbau.org
www.ikntbau.org
www.kintbau.org
www.ontbau.org
www.iontbau.org
www.ointbau.org
www.itbau.org
www.ibtbau.org
www.inbtbau.org
www.ibntbau.org
www.ihtbau.org
www.inhtbau.org
www.ihntbau.org
www.ijtbau.org
www.injtbau.org
www.imtbau.org
www.inmtbau.org
www.imntbau.org
www.inbau.org
www.inrbau.org
www.intrbau.org
www.inrtbau.org
www.infbau.org
www.intfbau.org
www.inftbau.org
www.ingbau.org
www.intgbau.org
www.ingtbau.org
www.inybau.org
www.intybau.org
www.inytbau.org
www.intau.org
www.intvau.org
www.intbvau.org
www.intvbau.org
www.intgau.org
www.intbgau.org
www.inthau.org
www.intbhau.org
www.inthbau.org
www.intnau.org
www.intbnau.org
www.intnbau.org
www.intbu.org
www.intbqu.org
www.intbaqu.org
www.intbqau.org
www.intbwu.org
www.intbawu.org
www.intbwau.org
www.intbsu.org
www.intbasu.org
www.intbsau.org
www.intbzu.org
www.intbazu.org
www.intbzau.org
www.intba.org
www.intbay.org
www.intbauy.org
www.intbayu.org
www.intbah.org
www.intbauh.org
www.intbahu.org
www.intbaj.org
www.intbauj.org
www.intbaju.org
www.intbai.org
www.intbaui.org
www.intbaiu.org
Last Tested: