Nabr.org Site Title
Why Animal Research?
Nabr.org Meta Description
NABR is dedicated to raising awareness of the role animals play in biomedical research. Find out more about the role the organization plays in devising sound public policy to help the scientific community.
Nabr.org Test Results
Nabr.org Mobile Performance: 28/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Minify CSS
Potential savings of 15 KiB
Minifying CSS files can reduce network payload sizes. Learn how to minify CSS.
Reduce the impact of third-party code
Third-party code blocked the main thread for 5,980 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.
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.
Properly size images
Potential savings of 12 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Eliminate render-blocking resources
Potential savings of 1,110 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 unused CSS
Potential savings of 70 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.
Minimize main-thread work
13.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
Reduce JavaScript execution time
9.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.
Avoid an excessive DOM size
1,243 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 initial server response time
Root document took 1,370 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more about the Time to First Byte metric.
Avoid multiple page redirects
Potential savings of 1,110 ms
Redirects introduce additional delays before the page can be loaded. Learn how to avoid page redirects.
Largest Contentful Paint element
6,990 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
Reduce unused JavaScript
Potential savings of 1,443 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.
Defer offscreen images
Potential savings of 4,229 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 images in next-gen formats
Potential savings of 7,980 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.
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
54 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid enormous network payloads
Total size was 14,340 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.
Efficiently encode images
Potential savings of 3,769 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
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`.
Max Potential First Input Delay
1,440 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
45.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
4.9 s
First Meaningful Paint measures when the primary content of a page is visible. Learn more about the First Meaningful Paint metric.
Nabr.org Mobile SEO: 75/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.
Links do not have descriptive text
10 links found
Descriptive link text helps search engines understand your content. Learn how to make links more accessible.
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
Nabr.org Mobile Best Practices: 41/100
Quick overview:
User Experience
Displays images with incorrect aspect ratio
Image display dimensions should match natural aspect ratio. Learn more about image aspect ratio.
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
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.
Uses third-party cookies
3 cookies found
Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.
Uses deprecated APIs
1 warning found
Deprecated APIs will eventually be removed from the browser. Learn more about deprecated APIs.
Nabr.org Mobile Accessibility: 67/100
Quick overview:
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.
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.
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.
`[aria-hidden="true"]` elements contain focusable descendents
Focusable descendents within an `aria-hidden="true"]` element prevent those interactive elements from being available to users of assistive technologies like screen readers. [Learn how `aria-hidden` affects focusable elements.
Values assigned to `role=""` are not valid ARIA roles.
ARIA `role`s enable assistive technologies to know the role of each element on the web page. If the `role` values are misspelled, not existing ARIA `role` values, or abstract roles, then the purpose of the element will not be communicated to users of assistive technologies. Learn more about ARIA roles.
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.
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.
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.
`<frame>` or `<iframe>` elements do not have a title
Screen reader users rely on frame titles to describe the contents of frames. Learn more about frame titles.
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.
Similar sites
Similar tests
www.nabr.com
www.nabr.net
www.nabr.org
www.nabr.info
www.nabr.biz
www.nabr.us
www.nabr.mobi
www.abr.org
www.nabr.org
www.babr.org
www.nbabr.org
www.bnabr.org
www.habr.org
www.nhabr.org
www.hnabr.org
www.jabr.org
www.njabr.org
www.jnabr.org
www.mabr.org
www.nmabr.org
www.mnabr.org
www.nbr.org
www.nqbr.org
www.naqbr.org
www.nqabr.org
www.nwbr.org
www.nawbr.org
www.nwabr.org
www.nsbr.org
www.nasbr.org
www.nsabr.org
www.nzbr.org
www.nazbr.org
www.nzabr.org
www.nar.org
www.navr.org
www.nabvr.org
www.navbr.org
www.nagr.org
www.nabgr.org
www.nagbr.org
www.nahr.org
www.nabhr.org
www.nahbr.org
www.nanr.org
www.nabnr.org
www.nanbr.org
www.nab.org
www.nabe.org
www.nabre.org
www.naber.org
www.nabd.org
www.nabrd.org
www.nabdr.org
www.nabf.org
www.nabrf.org
www.nabfr.org
www.nabt.org
www.nabrt.org
www.nabtr.org
www.nabr.net
www.nabr.org
www.nabr.info
www.nabr.biz
www.nabr.us
www.nabr.mobi
www.abr.org
www.nabr.org
www.babr.org
www.nbabr.org
www.bnabr.org
www.habr.org
www.nhabr.org
www.hnabr.org
www.jabr.org
www.njabr.org
www.jnabr.org
www.mabr.org
www.nmabr.org
www.mnabr.org
www.nbr.org
www.nqbr.org
www.naqbr.org
www.nqabr.org
www.nwbr.org
www.nawbr.org
www.nwabr.org
www.nsbr.org
www.nasbr.org
www.nsabr.org
www.nzbr.org
www.nazbr.org
www.nzabr.org
www.nar.org
www.navr.org
www.nabvr.org
www.navbr.org
www.nagr.org
www.nabgr.org
www.nagbr.org
www.nahr.org
www.nabhr.org
www.nahbr.org
www.nanr.org
www.nabnr.org
www.nanbr.org
www.nab.org
www.nabe.org
www.nabre.org
www.naber.org
www.nabd.org
www.nabrd.org
www.nabdr.org
www.nabf.org
www.nabrf.org
www.nabfr.org
www.nabt.org
www.nabrt.org
www.nabtr.org