Irn.org Site Title
Home - International Rivers NetworkInternational Rivers Network
Irn.org Meta Description
International Rivers Network is the leading organization working to halt the construction of destructive river development projects and to promote sound river management options worldwide.
Irn.org Test Results
Irn.org Mobile Performance: 92/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce unused JavaScript
Potential savings of 20 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.
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.
Eliminate render-blocking resources
Potential savings of 530 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.
Largest Contentful Paint element
3,000 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Properly size images
Potential savings of 7 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
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.
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
Serve static assets with an efficient cache policy
29 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
First Meaningful Paint
2.4 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Irn.org Mobile SEO: 100/100
Quick overview:
Irn.org Mobile Best Practices: 59/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.
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 about this errors in console diagnostic audit
User Experience
Serves images with low resolution
Image natural dimensions should be proportional to the display size and the pixel ratio to maximize image clarity. Learn how to provide responsive images.
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 about legible font sizes. Text is illegible because there's no viewport meta tag optimized for mobile screens.
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
Does not have a `<meta name="viewport">` tag with `width` or `initial-scale`
A `<meta name="viewport">` not only optimizes your app for mobile screen sizes, but also prevents a 300 millisecond delay to user input. Learn more about using the viewport meta tag. No `<meta name="viewport">` tag found
Trust and Safety
Does not use HTTPS
11 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.
Browser Compatibility
Page lacks the HTML doctype, thus triggering quirks-mode
Specifying a doctype prevents the browser from switching to quirks-mode. Learn more about the doctype declaration. Document must contain a doctype
Irn.org Mobile Accessibility: 54/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.
`<input type="image">` elements do not have `[alt]` text
When an image is being used as an `<input>` button, providing alternative text can help screen reader users understand the purpose of the button. Learn about input image alt text.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more about form element labels.
Contrast
These are opportunities to improve the legibility of your content.
Links rely on color to be distinguishable.
Low-contrast text is difficult or impossible for many users to read. Link text that is discernible improves the experience for users with low vision. Learn how to make links distinguishable.
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.
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.
Best practices
These items highlight common accessibility best practices.
Touch targets do not have sufficient size or spacing.
Touch targets with sufficient size and spacing help users who may have difficulty targeting small controls to activate the targets. Learn more about touch targets.
Similar sites
Similar tests
www.irn.com
www.irn.net
www.irn.org
www.irn.info
www.irn.biz
www.irn.us
www.irn.mobi
www.rn.org
www.irn.org
www.urn.org
www.iurn.org
www.uirn.org
www.jrn.org
www.ijrn.org
www.jirn.org
www.krn.org
www.ikrn.org
www.kirn.org
www.orn.org
www.iorn.org
www.oirn.org
www.in.org
www.ien.org
www.iren.org
www.iern.org
www.idn.org
www.irdn.org
www.idrn.org
www.ifn.org
www.irfn.org
www.ifrn.org
www.itn.org
www.irtn.org
www.itrn.org
www.ir.org
www.irb.org
www.irnb.org
www.irbn.org
www.irh.org
www.irnh.org
www.irhn.org
www.irj.org
www.irnj.org
www.irjn.org
www.irm.org
www.irnm.org
www.irmn.org
www.irn.net
www.irn.org
www.irn.info
www.irn.biz
www.irn.us
www.irn.mobi
www.rn.org
www.irn.org
www.urn.org
www.iurn.org
www.uirn.org
www.jrn.org
www.ijrn.org
www.jirn.org
www.krn.org
www.ikrn.org
www.kirn.org
www.orn.org
www.iorn.org
www.oirn.org
www.in.org
www.ien.org
www.iren.org
www.iern.org
www.idn.org
www.irdn.org
www.idrn.org
www.ifn.org
www.irfn.org
www.ifrn.org
www.itn.org
www.irtn.org
www.itrn.org
www.ir.org
www.irb.org
www.irnb.org
www.irbn.org
www.irh.org
www.irnh.org
www.irhn.org
www.irj.org
www.irnj.org
www.irjn.org
www.irm.org
www.irnm.org
www.irmn.org