Glif.app Site Title

glif - all prompts, no code AI sandbox • build AI workflows, apps, chatbots & more

Glif.app Test Results

Glif.app Mobile Performance: 10/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 590 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 how to minimize third-party impact.
Avoid an excessive DOM size
3,351 elements
A large DOM will increase memory usage, cause longer style calculations, and produce costly layout reflows. Learn how to avoid an excessive DOM size.
Reduce unused CSS
Potential savings of 18 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.
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 how to defer third-parties with a facade.
Reduce unused JavaScript
Potential savings of 511 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.
Eliminate render-blocking resources
Potential savings of 450 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.
Reduce JavaScript execution time
10.8 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to reduce Javascript execution time.
Largest Contentful Paint image was lazily loaded
Above-the-fold images that are lazily loaded render later in the page lifecycle, which can delay the largest contentful paint. Learn more about optimal lazy loading.
Avoid large layout shifts
8 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
Avoid multiple page redirects
Potential savings of 1,090 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
19,060 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Avoid serving legacy JavaScript to modern browsers
Potential savings of 28 KiB
Polyfills and transforms enable legacy browsers to use new JavaScript features. However, many aren't necessary for modern browsers. For your bundled JavaScript, adopt a modern script deployment strategy using module/nomodule feature detection to reduce the amount of code shipped to modern browsers, while retaining support for legacy browsers. Learn how to use modern JavaScript
Minimize main-thread work
18.8 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn how to minimize main-thread work
Avoid enormous network payloads
Total size was 3,309 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Defer offscreen images
Potential savings of 2 KiB
Consider lazy-loading offscreen and hidden images after all critical resources have finished loading to lower time to interactive. Learn how to defer offscreen images.
Serve static assets with an efficient cache policy
2 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
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 how to set image dimensions
Properly size images
Potential savings of 999 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Max Potential First Input Delay
4,520 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.
Time to Interactive
19.0 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
5.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.

Glif.app Mobile SEO: 85/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
13 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more about the meta description.

Glif.app Mobile Best Practices: 83/100
Quick overview:
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.
General
Missing source maps for large first-party JavaScript
Source maps translate minified code to the original source code. This helps developers debug in production. In addition, Lighthouse is able to provide further insights. Consider deploying source maps to take advantage of these benefits. Learn more about source maps.
Glif.app Mobile Accessibility: 80/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.
Buttons do not have an accessible name
When a button doesn't have an accessible name, screen readers announce it as "button", making it unusable for users who rely on screen readers. Learn how to make buttons more accessible.
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.
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.
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 sites
Similar tests
www.glif.com
www.glif.net
www.glif.org
www.glif.info
www.glif.biz
www.glif.us
www.glif.mobi
www.lif.app
www.glif.app
www.flif.app
www.gflif.app
www.fglif.app
www.vlif.app
www.gvlif.app
www.vglif.app
www.tlif.app
www.gtlif.app
www.tglif.app
www.blif.app
www.gblif.app
www.bglif.app
www.ylif.app
www.gylif.app
www.yglif.app
www.hlif.app
www.ghlif.app
www.hglif.app
www.gif.app
www.gpif.app
www.glpif.app
www.gplif.app
www.goif.app
www.gloif.app
www.golif.app
www.gkif.app
www.glkif.app
www.gklif.app
www.glf.app
www.gluf.app
www.gliuf.app
www.gluif.app
www.gljf.app
www.glijf.app
www.gljif.app
www.glkf.app
www.glikf.app
www.glof.app
www.gliof.app
www.gli.app
www.glic.app
www.glifc.app
www.glicf.app
www.glid.app
www.glifd.app
www.glidf.app
www.glir.app
www.glifr.app
www.glirf.app
www.glit.app
www.glift.app
www.glitf.app
www.glig.app
www.glifg.app
www.gligf.app
www.gliv.app
www.glifv.app
www.glivf.app
Last Tested: