Tools & Wizards About Us
em.no screenshot

Report Summary

  • 43

    Performance

    Renders faster than
    62% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 47% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

em.no

Elektriker i Oslo og Akershus - Elektriker'n Majorstua

Page Load Speed

6.4 sec in total

First Response

777 ms

Resources Loaded

5.4 sec

Page Rendered

272 ms

em.no screenshot

About Website

Welcome to em.no homepage info - get ready to check Em best content right away, or after learning these important things about em.no

Elektriker i Oslo og Akershus? Utfører alle typer elektrikeroppdrag, alt fra små til store prosjekter. Leverer kun produkter fra kjente kvalitetsmerker. >>

Visit em.no

Key Findings

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

Performance Metrics

em.no performance score

43

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.9 s

10/100

10%

LCP (Largest Contentful Paint)

Value10.7 s

0/100

25%

SI (Speed Index)

Value9.2 s

13/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.8 s

28/100

10%

Network Requests Diagram

em.no

777 ms

script.js

42 ms

style.css

116 ms

accessible-slick-theme.min.css

233 ms

responsive.css

340 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 77% of them (71 requests) were addressed to the original Em.no, 8% (7 requests) were made to Log.cookieyes.com and 7% (6 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Em.no.

Page Optimization Overview & Recommendations

Page size can be reduced by 126.1 kB (8%)

Content Size

1.5 MB

After Optimization

1.4 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Em.no main page is 1.5 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. 50% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 47.9 kB

  • Original 61.6 kB
  • After minification 56.3 kB
  • After compression 13.7 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. HTML code on this page is well minified. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 47.9 kB or 78% of the original size.

Image Optimization

-5%

Potential reduce by 51.8 kB

  • Original 1.1 MB
  • After minification 1.0 MB

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. Em images are well optimized though.

JavaScript Optimization

-6%

Potential reduce by 19.0 kB

  • Original 330.4 kB
  • After minification 330.4 kB
  • After compression 311.4 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

-12%

Potential reduce by 7.3 kB

  • Original 61.9 kB
  • After minification 61.9 kB
  • After compression 54.6 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. Em.no needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 12% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (71%)

Requests Now

72

After Optimization

21

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

em.no

em.no

777 ms

script.js

script.js

42 ms

style.css

style.css

116 ms

accessible-slick-theme.min.css

accessible-slick-theme.min.css

233 ms

responsive.css

responsive.css

340 ms

cv.css

cv.css

342 ms

style.min.css

style.min.css

454 ms

styles.css

styles.css

344 ms

blue.css

blue.css

344 ms

addthis_wordpress_public.min.css

addthis_wordpress_public.min.css

344 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

565 ms

modernizr.custom.js

modernizr.custom.js

453 ms

ddlevelsmenu.js

ddlevelsmenu.js

453 ms

ddlevelsmenu-invoke.js

ddlevelsmenu-invoke.js

454 ms

jquery.flexslider-min.js

jquery.flexslider-min.js

452 ms

js

js

74 ms

addthis_widget.js

addthis_widget.js

29 ms

shortcodes.css

shortcodes.css

562 ms

index.js

index.js

563 ms

index.js

index.js

555 ms

cv.js

cv.js

556 ms

ie.js

ie.js

662 ms

form-processor.js

form-processor.js

662 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

664 ms

jquery.polyglot.language.switcher.js

jquery.polyglot.language.switcher.js

665 ms

tinynav.min.js

tinynav.min.js

665 ms

jquery.validate.min.js

jquery.validate.min.js

666 ms

jquery.jcarousel.min.js

jquery.jcarousel.min.js

773 ms

jquery.ui.totop.min.js

jquery.ui.totop.min.js

772 ms

jquery-ui-1.10.0.custom.min.js

jquery-ui-1.10.0.custom.min.js

897 ms

jquery.fancybox.pack.js

jquery.fancybox.pack.js

775 ms

jquery.cycle.all.js

jquery.cycle.all.js

777 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

779 ms

jquery.fitvids.js

jquery.fitvids.js

885 ms

jquery.tweet.js

jquery.tweet.js

884 ms

jflickrfeed.min.js

jflickrfeed.min.js

887 ms

jquery.quicksand.js

jquery.quicksand.js

889 ms

jquery.touchSwipe.min.js

jquery.touchSwipe.min.js

891 ms

jquery.gmap.min.js

jquery.gmap.min.js

999 ms

log

log

412 ms

css

css

36 ms

css

css

52 ms

css

css

62 ms

html5-reset.css

html5-reset.css

903 ms

polyglot-language-switcher.css

polyglot-language-switcher.css

792 ms

flexslider.css

flexslider.css

687 ms

jquery.fancybox.css

jquery.fancybox.css

688 ms

mediaelementplayer.css

mediaelementplayer.css

1432 ms

shortcodes.css

shortcodes.css

793 ms

comment-reply.min.js

comment-reply.min.js

792 ms

custom.js

custom.js

684 ms

slick.min.js

slick.min.js

685 ms

SliderFullGallery.js

SliderFullGallery.js

685 ms

farmer.png

farmer.png

451 ms

em__logo.png

em__logo.png

169 ms

utelys_blaa.jpg

utelys_blaa.jpg

785 ms

utstilling_blaa-e1543846106730.jpg

utstilling_blaa-e1543846106730.jpg

338 ms

damekjokken_blaa.jpg

damekjokken_blaa.jpg

379 ms

nobo_blaa-e1543847104842.jpg

nobo_blaa-e1543847104842.jpg

380 ms

majorstua_blaa.jpg

majorstua_blaa.jpg

618 ms

Fridom1-e1543846664504.jpg

Fridom1-e1543846664504.jpg

452 ms

fastelektriker.png

fastelektriker.png

495 ms

pdf-logo.png

pdf-logo.png

496 ms

elkofront-1024x529.png

elkofront-1024x529.png

683 ms

em__logo-300x74.png

em__logo-300x74.png

582 ms

home.png

home.png

596 ms

phone.png

phone.png

596 ms

mail.png

mail.png

682 ms

clock.png

clock.png

709 ms

sJoA3LZUhMSAPV_u0qwiAQ-O5Xo.ttf

sJoA3LZUhMSAPV_u0qwiAQ-O5Xo.ttf

114 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsjZ0B4gaVc.ttf

128 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsiH0B4gaVc.ttf

138 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsgH1x4gaVc.ttf

143 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgsg-1x4gaVc.ttf

143 ms

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

memSYaGs126MiZpBA-UvWbX2vVnXBbObj2OVZyOOSr4dVJWUgshZ1x4gaVc.ttf

143 ms

blank.htm

blank.htm

930 ms

scroll-top.png

scroll-top.png

563 ms

ajax-loader.gif

ajax-loader.gif

1072 ms

slick.woff

slick.woff

1142 ms

log

log

236 ms

log

log

366 ms

addthis_widget.js

addthis_widget.js

44 ms

alert-56.png

alert-56.png

235 ms

arrow-right.png

arrow-right.png

234 ms

blank.htm

blank.htm

458 ms

slick.ttf

slick.ttf

452 ms

log

log

308 ms

log

log

286 ms

log

log

533 ms

addthis_widget.js

addthis_widget.js

119 ms

log

log

398 ms

slick.svg

slick.svg

420 ms

Accessibility Review

em.no accessibility score

79

Accessibility Issues

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

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

em.no best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

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

SEO Factors

em.no SEO score

91

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    NO

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Em.no can be misinterpreted by Google and other search engines. Our service has detected that Norwegian is used on the page, and it does not match the claimed English language. Our system also found out that Em.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

em.no

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