Corum.no Site Title

CORUM - HOME

Corum.no Meta Description

Corum AS

Corum.no Test Results

Corum.no Mobile Performance: 44/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,690 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.
Serve images in next-gen formats. Potential savings of 214 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.
Remove unused JavaScript. Potential savings of 224 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Remove unused CSS. Potential savings of 29 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.
Minify JavaScript. Potential savings of 8 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Preload key requests. Potential savings of 150 ms
Consider using `<link rel=preload>` to prioritize fetching resources that are currently requested later in page load. 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.
Reduce the impact of third-party code
Third-party code blocked the main thread for 750 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 more.
Serve static assets with an efficient cache policy
17 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Minimize main-thread work
2.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Reduce JavaScript execution time
1.6 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. 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
38 requests • 1,156 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Avoid long main-thread tasks
7 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid chaining critical requests
17 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.

Corum.no Mobile SEO: 100/100
Quick overview:

Corum.no Mobile Best Practices: 79/100
Quick overview:
Trust and Safety
Does not use HTTPS
22 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 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.
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.
Corum.no Mobile Progressive Web App: 39/100
Quick overview:
Fast and reliable
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.
`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.
Installable
Does not use HTTPS
22 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 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.
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 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.
PWA Optimized
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
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
Does not redirect HTTP traffic to HTTPS
If you've already set up 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 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.
Corum.no Mobile Accessibility: 97/100
Quick overview:
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.
Similar tests
www.corum.com
www.corum.net
www.corum.org
www.corum.info
www.corum.biz
www.corum.us
www.corum.mobi
www.orum.no
www.corum.no
www.xorum.no
www.cxorum.no
www.xcorum.no
www.dorum.no
www.cdorum.no
www.dcorum.no
www.forum.no
www.cforum.no
www.fcorum.no
www.vorum.no
www.cvorum.no
www.vcorum.no
www.crum.no
www.cirum.no
www.coirum.no
www.ciorum.no
www.ckrum.no
www.cokrum.no
www.ckorum.no
www.clrum.no
www.colrum.no
www.clorum.no
www.cprum.no
www.coprum.no
www.cporum.no
www.coum.no
www.coeum.no
www.coreum.no
www.coerum.no
www.codum.no
www.cordum.no
www.codrum.no
www.cofum.no
www.corfum.no
www.cofrum.no
www.cotum.no
www.cortum.no
www.cotrum.no
www.corm.no
www.corym.no
www.coruym.no
www.coryum.no
www.corhm.no
www.coruhm.no
www.corhum.no
www.corjm.no
www.corujm.no
www.corjum.no
www.corim.no
www.coruim.no
www.corium.no
www.coru.no
www.corun.no
www.corumn.no
www.corunm.no
www.coruj.no
www.corumj.no
www.coruk.no
www.corumk.no
www.corukm.no
Last Tested: