Moods.no Site Title
Moods.no | Menswear inspired by stories
Moods.no Meta Description
Welcome to the Moods webshop! We create menswear and stories inspired by those who dare to do more. Over 80,000 orders delivered globally. Join the mood!
Moods.no Test Results
Moods.no Mobile Performance: 36/100
Quick overview:
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Defer offscreen images
Potential savings of 43 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 2,240 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 large layout shifts
2 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
Reduce unused JavaScript
Potential savings of 325 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.
Minimize main-thread work
9.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 unused CSS
Potential savings of 217 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.
Properly size images
Potential savings of 1,893 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn how to size images.
Largest Contentful Paint element
11,200 ms
This is the largest contentful element painted within the viewport. Learn more about the Largest Contentful Paint element
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 an excessive DOM size
1,916 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 JavaScript execution time
5.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 reduce Javascript execution time.
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
Efficiently encode images
Potential savings of 132 KiB
Optimized images load faster and consume less cellular data. Learn how to efficiently encode images.
Serve images in next-gen formats
Potential savings of 310 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.
Avoid enormous network payloads
Total size was 6,403 KiB
Large network payloads cost users real money and are highly correlated with long load times. Learn how to reduce payload sizes.
Serve static assets with an efficient cache policy
51 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more about efficient cache policies.
Avoid `document.write()`
For users on slow connections, external scripts dynamically injected via `document.write()` can delay page load by tens of seconds. Learn how to avoid document.write().
Avoid serving legacy JavaScript to modern browsers
Potential savings of 52 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
Remove duplicate modules in JavaScript bundles
Potential savings of 14 KiB
Remove large, duplicate JavaScript modules from bundles to reduce unnecessary bytes consumed by network activity.
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.
Time to Interactive
25.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.
Max Potential First Input Delay
710 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.
Moods.no Mobile SEO: 92/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.
Moods.no Mobile Best Practices: 55/100
Quick overview:
General
Uses third-party cookies
1 cookie found
Support for third-party cookies will be removed in a future version of Chrome. Learn more about phasing out third-party cookies.
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
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 redirect HTTP traffic to HTTPS
Make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not use HTTPS
56 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.
Moods.no Mobile Accessibility: 78/100
Quick overview:
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.
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.
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.
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.
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.
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.
Similar sites
Similar tests
www.moods.com
www.moods.net
www.moods.org
www.moods.info
www.moods.biz
www.moods.us
www.moods.mobi
www.oods.no
www.moods.no
www.noods.no
www.mnoods.no
www.nmoods.no
www.joods.no
www.mjoods.no
www.jmoods.no
www.koods.no
www.mkoods.no
www.kmoods.no
www.mods.no
www.miods.no
www.moiods.no
www.mioods.no
www.mkods.no
www.mokods.no
www.mlods.no
www.molods.no
www.mloods.no
www.mpods.no
www.mopods.no
www.mpoods.no
www.moids.no
www.mooids.no
www.mokds.no
www.mookds.no
www.molds.no
www.moolds.no
www.mopds.no
www.moopds.no
www.moos.no
www.mooxs.no
www.moodxs.no
www.mooxds.no
www.mooss.no
www.moodss.no
www.moosds.no
www.mooes.no
www.moodes.no
www.mooeds.no
www.moors.no
www.moodrs.no
www.moords.no
www.moofs.no
www.moodfs.no
www.moofds.no
www.moocs.no
www.moodcs.no
www.moocds.no
www.mood.no
www.moodw.no
www.moodsw.no
www.moodws.no
www.moode.no
www.moodse.no
www.moodd.no
www.moodsd.no
www.moodds.no
www.moodz.no
www.moodsz.no
www.moodzs.no
www.moodx.no
www.moodsx.no
www.mooda.no
www.moodsa.no
www.moodas.no
www.moods.net
www.moods.org
www.moods.info
www.moods.biz
www.moods.us
www.moods.mobi
www.oods.no
www.moods.no
www.noods.no
www.mnoods.no
www.nmoods.no
www.joods.no
www.mjoods.no
www.jmoods.no
www.koods.no
www.mkoods.no
www.kmoods.no
www.mods.no
www.miods.no
www.moiods.no
www.mioods.no
www.mkods.no
www.mokods.no
www.mlods.no
www.molods.no
www.mloods.no
www.mpods.no
www.mopods.no
www.mpoods.no
www.moids.no
www.mooids.no
www.mokds.no
www.mookds.no
www.molds.no
www.moolds.no
www.mopds.no
www.moopds.no
www.moos.no
www.mooxs.no
www.moodxs.no
www.mooxds.no
www.mooss.no
www.moodss.no
www.moosds.no
www.mooes.no
www.moodes.no
www.mooeds.no
www.moors.no
www.moodrs.no
www.moords.no
www.moofs.no
www.moodfs.no
www.moofds.no
www.moocs.no
www.moodcs.no
www.moocds.no
www.mood.no
www.moodw.no
www.moodsw.no
www.moodws.no
www.moode.no
www.moodse.no
www.moodd.no
www.moodsd.no
www.moodds.no
www.moodz.no
www.moodsz.no
www.moodzs.no
www.moodx.no
www.moodsx.no
www.mooda.no
www.moodsa.no
www.moodas.no