Tools & Wizards About Us
pasientsky.no screenshot

Report Summary

  • 19

    Performance

    Renders faster than
    36% of other websites

  • 74

    Accessibility

    Visual factors better than
    that of 40% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

pasientsky.no

EG Pasientsky - Bedre, raskere og billigere pasient­behandling

Page Load Speed

4.4 sec in total

First Response

230 ms

Resources Loaded

3.6 sec

Page Rendered

591 ms

pasientsky.no screenshot

About Website

Click here to check amazing Pasientsky content for Norway. Otherwise, check out these important facts you probably never knew about pasientsky.no

Ett system for hele klinikken. Perfekte for selvstendige og offentlige terapeuter, tverrfaglige klinikker, kiropraktorer, og fysioterapeuter.

Visit pasientsky.no

Key Findings

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

Performance Metrics

pasientsky.no performance score

19

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.2 s

3/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value10.2 s

8/100

10%

TBT (Total Blocking Time)

Value780 ms

37/100

30%

CLS (Cumulative Layout Shift)

Value0.302

39/100

15%

TTI (Time to Interactive)

Value16.1 s

6/100

10%

Network Requests Diagram

pasientsky.no

230 ms

641 ms

iframeResizer.min.js

56 ms

screen.css

214 ms

vendor.bundle.js

217 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pasientsky.no, 81% (43 requests) were made to Eg.no and 6% (3 requests) were made to Go.eg.no. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Eg.dk.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (72%)

Content Size

2.1 MB

After Optimization

573.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pasientsky.no main page is 2.1 MB. This result falls beyond the top 1M of websites and identifies a large and not optimized web page that may take ages to load. 25% of websites need less resources to load. CSS take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 69.4 kB

  • Original 83.3 kB
  • After minification 73.3 kB
  • After compression 13.9 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 10.0 kB, which is 12% 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 69.4 kB or 83% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 212.1 kB
  • After minification 212.1 kB

Image size optimization can help to speed up a website loading time. The chart above shows the difference between the size before and after optimization. Pasientsky images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 261.6 kB

  • Original 478.7 kB
  • After minification 478.7 kB
  • After compression 217.0 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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 261.6 kB or 55% of the original size.

CSS Optimization

-90%

Potential reduce by 1.2 MB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 130.3 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. Pasientsky.no needs all CSS files to be minified and compressed as it can save up to 1.2 MB or 90% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (17%)

Requests Now

41

After Optimization

34

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pasientsky.no

pasientsky.no

230 ms

641 ms

iframeResizer.min.js

iframeResizer.min.js

56 ms

screen.css

screen.css

214 ms

vendor.bundle.js

vendor.bundle.js

217 ms

EG.bundle.js

EG.bundle.js

325 ms

find.js

find.js

39 ms

screen.css

screen.css

757 ms

vendor.bundle.js

vendor.bundle.js

436 ms

eg.bundle.js

eg.bundle.js

230 ms

gtm.js

gtm.js

549 ms

eg-logo.svg

eg-logo.svg

210 ms

arrow-right-white.svg

arrow-right-white.svg

208 ms

icon-menu-open-blue.svg

icon-menu-open-blue.svg

209 ms

arrow-right-blue.svg

arrow-right-blue.svg

317 ms

icon-search-open-blue.svg

icon-search-open-blue.svg

318 ms

eg-pasientsky-hero-img-sm.png

eg-pasientsky-hero-img-sm.png

759 ms

udtraek-analyse-kvalitetsikr-simulering.svg

udtraek-analyse-kvalitetsikr-simulering.svg

430 ms

tips-i-systemet.svg

tips-i-systemet.svg

438 ms

administrer-alt.svg

administrer-alt.svg

534 ms

sok-og-filtrer-alle-journalforinger.svg

sok-og-filtrer-alle-journalforinger.svg

546 ms

snarveier.svg

snarveier.svg

542 ms

journalmaler.svg

journalmaler.svg

556 ms

regningskortet-fylles-ut-automatisk.svg

regningskortet-fylles-ut-automatisk.svg

558 ms

online-opsigelse.svg

online-opsigelse.svg

646 ms

tilgangs--og-rettighetsstyring.svg

tilgangs--og-rettighetsstyring.svg

657 ms

automatisk-lagring-og-versjonskontroll.svg

automatisk-lagring-og-versjonskontroll.svg

655 ms

eg-ps-kryptering.svg

eg-ps-kryptering.svg

672 ms

anonyme-svar.svg

anonyme-svar.svg

670 ms

trygg-forskrivning-med-varslingssystemer.svg

trygg-forskrivning-med-varslingssystemer.svg

757 ms

innsynslogg.svg

innsynslogg.svg

768 ms

vum2.svg

vum2.svg

769 ms

administrer-pasientopplysninger.svg

administrer-pasientopplysninger.svg

788 ms

eg-ps-cloud.svg

eg-ps-cloud.svg

789 ms

interne-meldinger.svg

interne-meldinger.svg

872 ms

visning-etter-dag-maned-ar.svg

visning-etter-dag-maned-ar.svg

871 ms

fa-paminnelser-om-ufakturerte-timer.svg

fa-paminnelser-om-ufakturerte-timer.svg

879 ms

integrert-med-betalingsterminaler.svg

integrert-med-betalingsterminaler.svg

880 ms

arrow-right-red.svg

arrow-right-red.svg

835 ms

NeoSansStd-Regular.woff

NeoSansStd-Regular.woff

833 ms

NeoSansStd-Medium.woff

NeoSansStd-Medium.woff

913 ms

NeoSansStd-Bold.woff

NeoSansStd-Bold.woff

910 ms

3kpgrz

3kpgrz

426 ms

3kpgsh

3kpgsh

361 ms

sprite.symbol.svg

sprite.symbol.svg

863 ms

screen.css

screen.css

1104 ms

jquery-3.5.0.slim.min.js

jquery-3.5.0.slim.min.js

16 ms

iframeResizer.contentWindow.min.js

iframeResizer.contentWindow.min.js

13 ms

piUtils.js

piUtils.js

41 ms

neosansstd-regular.woff

neosansstd-regular.woff

111 ms

neosansstd-bold.woff

neosansstd-bold.woff

215 ms

neosansstd-medium.woff

neosansstd-medium.woff

112 ms

sprite.symbol.svg

sprite.symbol.svg

135 ms

Accessibility Review

pasientsky.no accessibility score

74

Accessibility Issues

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.

Impact

Issue

High

[aria-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

pasientsky.no best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

pasientsky.no SEO score

93

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

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 Pasientsky.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 Pasientsky.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

pasientsky.no

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