Tools & Wizards About Us
eppens.se screenshot

Report Summary

  • 31

    Performance

    Renders faster than
    51% of other websites

  • 84

    Accessibility

    Visual factors better than
    that of 57% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 79

    SEO

    Google-friendlier than
    40% of websites

eppens.se

Erfaren arkitekt i Stockholm - Eppens Arkitektur AB

Page Load Speed

3.5 sec in total

First Response

681 ms

Resources Loaded

2.4 sec

Page Rendered

329 ms

eppens.se screenshot

About Website

Welcome to eppens.se homepage info - get ready to check Eppens best content right away, or after learning these important things about eppens.se

Att anlita en arkitekt ska ge mervärden - vi jobbar lyhört och följsamt för att säkerställa hållbara och omtyckta lösningar i varje projekt.

Visit eppens.se

Key Findings

We analyzed Eppens.se page load time and found that the first response time was 681 ms and then it took 2.8 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

eppens.se performance score

31

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value12.4 s

0/100

25%

SI (Speed Index)

Value8.2 s

20/100

10%

TBT (Total Blocking Time)

Value1,340 ms

17/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.1 s

16/100

10%

Network Requests Diagram

eppens.se

681 ms

Eppens_with_svg.css

115 ms

style.css

221 ms

style.css

277 ms

jquery-1.10.0-min.js

347 ms

Our browser made a total of 15 requests to load all elements on the main page. We found that 93% of them (14 requests) were addressed to the original Eppens.se, 7% (1 request) were made to Hello.myfonts.net. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Eppens.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.9 kB (13%)

Content Size

1.5 MB

After Optimization

1.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Eppens.se 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. 20% of websites need less resources to load. Images take 1.3 MB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 2.9 kB

  • Original 3.8 kB
  • After minification 3.4 kB
  • After compression 923 B

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 2.9 kB or 76% of the original size.

Image Optimization

-3%

Potential reduce by 34.7 kB

  • Original 1.3 MB
  • After minification 1.3 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. Eppens images are well optimized though.

JavaScript Optimization

-76%

Potential reduce by 145.9 kB

  • Original 191.7 kB
  • After minification 144.5 kB
  • After compression 45.8 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 145.9 kB or 76% of the original size.

CSS Optimization

-81%

Potential reduce by 12.4 kB

  • Original 15.3 kB
  • After minification 10.4 kB
  • After compression 2.9 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. Eppens.se needs all CSS files to be minified and compressed as it can save up to 12.4 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 8 (67%)

Requests Now

12

After Optimization

4

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

eppens.se

eppens.se

681 ms

Eppens_with_svg.css

Eppens_with_svg.css

115 ms

style.css

style.css

221 ms

style.css

style.css

277 ms

jquery-1.10.0-min.js

jquery-1.10.0-min.js

347 ms

jquery-ui-1.8.23.custom.min.js

jquery-ui-1.8.23.custom.min.js

227 ms

jquery.mousewheel.js

jquery.mousewheel.js

228 ms

jquery.kinetic.js

jquery.kinetic.js

235 ms

jquery.smoothdivscroll-1.3-min.js

jquery.smoothdivscroll-1.3-min.js

330 ms

script.js

script.js

339 ms

logo.png

logo.png

450 ms

2b507c

2b507c

32 ms

home_bg_eppens.jpg

home_bg_eppens.jpg

1484 ms

2B507C_1_0.woff

2B507C_1_0.woff

253 ms

2B507C_0_0.woff

2B507C_0_0.woff

262 ms

Accessibility Review

eppens.se accessibility score

84

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

Image elements do not have [alt] attributes

Best Practices

eppens.se best practices score

92

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

Page has valid source maps

SEO Factors

eppens.se SEO score

79

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

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Image elements do not have [alt] attributes

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 doesn't use legible font sizes

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Eppens.se can be misinterpreted by Google and other search engines. Our service has detected that Swedish is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Eppens.se 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

eppens.se

Open Graph description is not detected on the main page of Eppens. Lack of Open Graph description can be counter-productive for their social media presence, as such a description allows converting a website homepage (or other pages) into good-looking, rich and well-structured posts, when it is being shared on Facebook and other social media. For example, adding the following code snippet into HTML <head> tag will help to represent this web page correctly in social networks: