Wfm-igp.org Site Title

Our mission is to create more effective, transparent, and accountable global governance leading to democratic world federation - WFM/IGP

Wfm-igp.org Test Results

Wfm-igp.org Mobile Performance: 20/100
Quick overview:
Time to Interactive
24.6 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
1,140 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
4.4 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.
Avoid large layout shifts
6 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
Minimize main-thread work
9.5 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 multiple page redirects
Potential savings of 630 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Reduce unused CSS
Potential savings of 169 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 an excessive DOM size
952 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.
Largest Contentful Paint element
18,020 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce the impact of third-party code
Third-party code blocked the main thread for 3,120 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.
Serve images in next-gen formats
Potential savings of 1,263 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.
Eliminate render-blocking resources
Potential savings of 2,420 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.
Defer offscreen images
Potential savings of 192 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.
Efficiently encode images
Potential savings of 822 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Reduce unused JavaScript
Potential savings of 856 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.
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 JavaScript execution time
6.1 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.
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`.
Avoid enormous network payloads
Total size was 4,288 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
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 about adopting passive event listeners.
Serve static assets with an efficient cache policy
81 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid serving legacy JavaScript to modern browsers
Potential savings of 0 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

Wfm-igp.org 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.
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.
Links do not have descriptive text
7 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.

Wfm-igp.org Mobile Best Practices: 79/100
Quick overview:
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.
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.
Wfm-igp.org Mobile Accessibility: 84/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.
Elements with visible text labels do not have matching accessible names.
Visible text labels that do not match the accessible name can result in a confusing experience for screen reader users. Learn more about accessible names.
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.
Skip links are not focusable.
Including a skip link can help users skip to the main content to save time. Learn more about skip links.
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.
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.
Some elements have a `[tabindex]` value greater than 0
A value greater than 0 implies an explicit navigation ordering. Although technically valid, this often creates frustrating experiences for users who rely on assistive technologies. Learn more about the `tabindex` 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.
Similar tests
www.wfm-igp.com
www.wfm-igp.net
www.wfm-igp.org
www.wfm-igp.info
www.wfm-igp.biz
www.wfm-igp.us
www.wfm-igp.mobi
www.fm-igp.org
www.wfm-igp.org
www.qfm-igp.org
www.wqfm-igp.org
www.qwfm-igp.org
www.afm-igp.org
www.wafm-igp.org
www.awfm-igp.org
www.sfm-igp.org
www.wsfm-igp.org
www.swfm-igp.org
www.efm-igp.org
www.wefm-igp.org
www.ewfm-igp.org
www.wm-igp.org
www.wcm-igp.org
www.wfcm-igp.org
www.wcfm-igp.org
www.wdm-igp.org
www.wfdm-igp.org
www.wdfm-igp.org
www.wrm-igp.org
www.wfrm-igp.org
www.wrfm-igp.org
www.wtm-igp.org
www.wftm-igp.org
www.wtfm-igp.org
www.wgm-igp.org
www.wfgm-igp.org
www.wgfm-igp.org
www.wvm-igp.org
www.wfvm-igp.org
www.wvfm-igp.org
www.wf-igp.org
www.wfn-igp.org
www.wfmn-igp.org
www.wfnm-igp.org
www.wfj-igp.org
www.wfmj-igp.org
www.wfjm-igp.org
www.wfk-igp.org
www.wfmk-igp.org
www.wfkm-igp.org
www.wfmigp.org
www.wfm-gp.org
www.wfm-ugp.org
www.wfm-iugp.org
www.wfm-uigp.org
www.wfm-jgp.org
www.wfm-ijgp.org
www.wfm-jigp.org
www.wfm-kgp.org
www.wfm-ikgp.org
www.wfm-kigp.org
www.wfm-ogp.org
www.wfm-iogp.org
www.wfm-oigp.org
www.wfm-ip.org
www.wfm-ifp.org
www.wfm-igfp.org
www.wfm-ifgp.org
www.wfm-ivp.org
www.wfm-igvp.org
www.wfm-ivgp.org
www.wfm-itp.org
www.wfm-igtp.org
www.wfm-itgp.org
www.wfm-ibp.org
www.wfm-igbp.org
www.wfm-ibgp.org
www.wfm-iyp.org
www.wfm-igyp.org
www.wfm-iygp.org
www.wfm-ihp.org
www.wfm-ighp.org
www.wfm-ihgp.org
www.wfm-ig.org
www.wfm-igo.org
www.wfm-igpo.org
www.wfm-igop.org
www.wfm-igl.org
www.wfm-igpl.org
www.wfm-iglp.org
Last Tested: