Tools & Wizards About Us
episerver.no screenshot

Report Summary

  • 2

    Performance

    Renders faster than
    20% of other websites

  • 96

    Accessibility

    Visual factors better than
    that of 88% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

episerver.no

Digitale opplevelser som engasjerer og skaper verdi - Optimizely

Page Load Speed

3 sec in total

First Response

439 ms

Resources Loaded

2 sec

Page Rendered

528 ms

episerver.no screenshot

About Website

Visit episerver.no now to see the best up-to-date Episerver content for Norway and also check out these interesting facts you probably never knew about episerver.no

Vår plattform for digitale opplevelser gjør det mulig for virksomheter å orkestrere, konvertere og eksperimentere

Visit episerver.no

Key Findings

We analyzed Episerver.no page load time and found that the first response time was 439 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

episerver.no performance score

2

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value7.5 s

4/100

25%

SI (Speed Index)

Value10.8 s

7/100

10%

TBT (Total Blocking Time)

Value6,310 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.012

2/100

15%

TTI (Time to Interactive)

Value20.7 s

2/100

10%

Network Requests Diagram

episerver.no

439 ms

www.episerver.no

533 ms

240 ms

zaius-min.js

46 ms

ia.js

42 ms

Our browser made a total of 47 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Episerver.no, 79% (37 requests) were made to Optimizely.com and 4% (2 requests) were made to Learn.optimizely.com. The less responsive or slowest element that took the longest time to load (533 ms) belongs to the original domain Episerver.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 331.4 kB (67%)

Content Size

494.9 kB

After Optimization

163.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Episerver.no main page is 494.9 kB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 55% of websites need less resources to load. HTML takes 377.6 kB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 331.1 kB

  • Original 377.6 kB
  • After minification 286.5 kB
  • After compression 46.5 kB

HTML content can be minified and compressed by a website’s server. The most efficient way is to compress content using GZIP which reduces data amount travelling through the network between server and browser. This page needs HTML code to be minified as it can gain 91.1 kB, which is 24% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 331.1 kB or 88% of the original size.

JavaScript Optimization

-0%

Potential reduce by 40 B

  • Original 62.3 kB
  • After minification 62.3 kB
  • After compression 62.3 kB

It’s better to minify JavaScript in order to improve website performance. The diagram shows the current total size of all JavaScript files against the prospective JavaScript size after its minification and compression. This website has mostly compressed JavaScripts.

CSS Optimization

-1%

Potential reduce by 329 B

  • Original 55.1 kB
  • After minification 55.1 kB
  • After compression 54.8 kB

CSS files minification is very important to reduce a web page rendering time. The faster CSS files can load, the earlier a page can be rendered. Episerver.no has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 31 (76%)

Requests Now

41

After Optimization

10

  • Images
  • JavaScript
  • CSS

The browser has sent 41 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Episerver. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 10 to 1 for JavaScripts and from 14 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

episerver.no

episerver.no

439 ms

www.episerver.no

www.episerver.no

533 ms

240 ms

zaius-min.js

zaius-min.js

46 ms

ia.js

ia.js

42 ms

analytics_2c549e58b1ac477abbecdb2a93599aac.js

analytics_2c549e58b1ac477abbecdb2a93599aac.js

40 ms

EPiServerForms.css

EPiServerForms.css

72 ms

home.js

home.js

65 ms

tag.js

tag.js

105 ms

entry-client-0fb26ced.css

entry-client-0fb26ced.css

69 ms

opti-grid.component-52931616.css

opti-grid.component-52931616.css

56 ms

container-9be9832a.css

container-9be9832a.css

55 ms

text.component-cddbbd19.css

text.component-cddbbd19.css

79 ms

highlight.component-eb3c70c8.css

highlight.component-eb3c70c8.css

63 ms

card.component-4e2d1c7a.css

card.component-4e2d1c7a.css

79 ms

card-default-4eff1a6a.css

card-default-4eff1a6a.css

105 ms

_card-76bcd469.css

_card-76bcd469.css

103 ms

custom-form-5aed9bec.css

custom-form-5aed9bec.css

105 ms

custom-checkbox-f40a94fb.css

custom-checkbox-f40a94fb.css

108 ms

custom-radio-737ddd70.css

custom-radio-737ddd70.css

109 ms

primary-footer.component-ad9d0456.css

primary-footer.component-ad9d0456.css

110 ms

cookie-consent.component-90e97e90.css

cookie-consent.component-90e97e90.css

138 ms

entry-client-2e942e88.js

entry-client-2e942e88.js

325 ms

jquery-3.5.1.min.js

jquery-3.5.1.min.js

127 ms

EPiServerForms.min.js

EPiServerForms.min.js

315 ms

optimizely-form-container-events.js

optimizely-form-container-events.js

126 ms

ia.gif

ia.gif

40 ms

ai.2.gbl.min.js

ai.2.gbl.min.js

38 ms

gtm.js

gtm.js

238 ms

hero-mask-dedbe392.svg

hero-mask-dedbe392.svg

77 ms

hero-highlight-809b0508.svg

hero-highlight-809b0508.svg

78 ms

logo_xerox_white_100x300.svg

logo_xerox_white_100x300.svg

76 ms

logo_hp-white2.svg

logo_hp-white2.svg

72 ms

stat-up-arrow-d30ff285.svg

stat-up-arrow-d30ff285.svg

72 ms

logo_ameripride_white_100x3002.svg

logo_ameripride_white_100x3002.svg

73 ms

80 ms

google-analytics-icon.svg

google-analytics-icon.svg

192 ms

siteimprove-icon.svg

siteimprove-icon.svg

79 ms

stripe-icon.svg

stripe-icon.svg

78 ms

microsoft_365_2022.svg

microsoft_365_2022.svg

82 ms

figma_icon.svg

figma_icon.svg

189 ms

half-circle-icon.svg

half-circle-icon.svg

196 ms

radio-bg-grey.svg

radio-bg-grey.svg

194 ms

radio-bg-light-blue.svg

radio-bg-light-blue.svg

192 ms

optimizely_symbol_full-color.svg

optimizely_symbol_full-color.svg

193 ms

Figtree-VariableFont_wght-583e9c3c.ttf

Figtree-VariableFont_wght-583e9c3c.ttf

113 ms

tooltip-grey.svg

tooltip-grey.svg

129 ms

Accessibility Review

episerver.no accessibility score

96

Accessibility Issues

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending 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.

Impact

Issue

High

Links do not have a discernible name

Best Practices

episerver.no best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

episerver.no SEO score

100

Search Engine Optimization Advices

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](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    NO

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Episerver.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it matches the claimed language. Our system also found out that Episerver.no main page’s claimed encoding is utf-8. Use of this encoding format is the best practice as the main page visitors from all over the world won’t have any issues with symbol transcription.

Social Sharing Optimization

episerver.no

Open Graph data is detected on the main page of Episerver. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: