Wrlc.org Site Title

Welcome to the Washington Research Library Consortium | Washington Research Library Consortium

Wrlc.org Test Results

Wrlc.org Mobile Performance: 52/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 2,570 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Enable text compression. Potential savings of 171 KiB
Text-based resources should be served with compression (gzip, deflate or brotli) to minimize total network bytes. Learn more.
Serve images in next-gen formats. Potential savings of 134 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Preload key requests. Potential savings of 600 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. Learn more.
Properly size images. Potential savings of 58 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Remove unused CSS. Potential savings of 74 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Efficiently encode images. Potential savings of 56 KiB
Optimized images load faster and consume less cellular data. Learn more.
Minify JavaScript. Potential savings of 39 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Remove unused JavaScript. Potential savings of 36 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
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.
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.
Avoid chaining critical requests
31 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Avoid long main-thread tasks
4 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Keep request counts low and transfer sizes small
42 requests • 539 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Wrlc.org Mobile SEO: 71/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.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
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 More
Mobile Friendly
Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. Learn more.
Tap targets are not sized appropriately
31% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Wrlc.org Mobile Best Practices: 69/100
Quick overview:
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 more.
Trust and Safety
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
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 servedover 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.
Includes front-end JavaScript libraries with known security vulnerabilities
7 vulnerabilities detected
Some third-party scripts may contain known security vulnerabilities that are easily identified and exploited by attackers. Learn more.
Wrlc.org Mobile Progressive Web App: 46/100
Quick overview:
PWA Optimized
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 more. No manifest was fetched
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 more. The viewport size of 366px does not match the window size of 360px.
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. 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. Failures: No manifest was fetched.
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
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 servedover 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.
Does not register a service worker that controls page and `start_url`
The 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. Learn more.
Wrlc.org Mobile Accessibility: 72/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.
Form elements do not have associated labels
Labels ensure that form controls are announced properly by assistive technologies, like screen readers. Learn more.
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.
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.
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.
Similar tests
www.wrlc.com
www.wrlc.net
www.wrlc.org
www.wrlc.info
www.wrlc.biz
www.wrlc.us
www.wrlc.mobi
www.rlc.org
www.wrlc.org
www.qrlc.org
www.wqrlc.org
www.qwrlc.org
www.arlc.org
www.warlc.org
www.awrlc.org
www.srlc.org
www.wsrlc.org
www.swrlc.org
www.erlc.org
www.werlc.org
www.ewrlc.org
www.wlc.org
www.welc.org
www.wrelc.org
www.wdlc.org
www.wrdlc.org
www.wdrlc.org
www.wflc.org
www.wrflc.org
www.wfrlc.org
www.wtlc.org
www.wrtlc.org
www.wtrlc.org
www.wrc.org
www.wrpc.org
www.wrlpc.org
www.wrplc.org
www.wroc.org
www.wrloc.org
www.wrolc.org
www.wrkc.org
www.wrlkc.org
www.wrklc.org
www.wrl.org
www.wrlx.org
www.wrlcx.org
www.wrlxc.org
www.wrld.org
www.wrlcd.org
www.wrldc.org
www.wrlf.org
www.wrlcf.org
www.wrlfc.org
www.wrlv.org
www.wrlcv.org
www.wrlvc.org
Last Tested: