Tools & Wizards About Us
lepigen.se screenshot

Report Summary

  • 67

    Performance

    Renders faster than
    79% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 97

    SEO

    Google-friendlier than
    91% of websites

lepigen.se

Effektiv viktminskning | Gå ner i vikt med Lepigen

Page Load Speed

7.4 sec in total

First Response

509 ms

Resources Loaded

6.5 sec

Page Rendered

362 ms

lepigen.se screenshot

About Website

Visit lepigen.se now to see the best up-to-date Lepigen content and also check out these interesting facts you probably never knew about lepigen.se

Upptäck våra premiumprodukter för effektiv viktminskning, speciellt framtagna för att stödja dig i din strävan efter välbefinnande och vitalitet.

Visit lepigen.se

Key Findings

We analyzed Lepigen.se page load time and found that the first response time was 509 ms and then it took 6.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

lepigen.se performance score

67

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

60/100

10%

LCP (Largest Contentful Paint)

Value4.9 s

29/100

25%

SI (Speed Index)

Value7.2 s

30/100

10%

TBT (Total Blocking Time)

Value210 ms

89/100

30%

CLS (Cumulative Layout Shift)

Value0.03

100/100

15%

TTI (Time to Interactive)

Value3.9 s

88/100

10%

Network Requests Diagram

lepigen.se

509 ms

lepigen.se

3854 ms

main.min.css

108 ms

style.min.css

217 ms

cookie-law-info-public.css

314 ms

Our browser made a total of 48 requests to load all elements on the main page. We found that 98% of them (47 requests) were addressed to the original Lepigen.se, 2% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (3.9 sec) belongs to the original domain Lepigen.se.

Page Optimization Overview & Recommendations

Page size can be reduced by 195.3 kB (21%)

Content Size

924.2 kB

After Optimization

728.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lepigen.se main page is 924.2 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. 35% of websites need less resources to load. Images take 584.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 152.8 kB

  • Original 186.8 kB
  • After minification 184.7 kB
  • After compression 33.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. 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 152.8 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 40.1 kB

  • Original 584.3 kB
  • After minification 544.2 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. Lepigen images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 1.2 kB

  • Original 85.5 kB
  • After minification 85.5 kB
  • After compression 84.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

-2%

Potential reduce by 1.2 kB

  • Original 67.7 kB
  • After minification 67.7 kB
  • After compression 66.5 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. Lepigen.se has all CSS files already compressed.

Requests Breakdown

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

Requests Now

46

After Optimization

11

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lepigen.se

lepigen.se

509 ms

lepigen.se

lepigen.se

3854 ms

main.min.css

main.min.css

108 ms

style.min.css

style.min.css

217 ms

cookie-law-info-public.css

cookie-law-info-public.css

314 ms

cookie-law-info-gdpr.css

cookie-law-info-gdpr.css

316 ms

woocommerce-layout-grid.min.css

woocommerce-layout-grid.min.css

316 ms

woocommerce-grid.min.css

woocommerce-grid.min.css

424 ms

spectra-block-positioning.min.css

spectra-block-positioning.min.css

316 ms

uag-css-107290.css

uag-css-107290.css

323 ms

astra-addon-65ce68338a56e3-91434159.css

astra-addon-65ce68338a56e3-91434159.css

417 ms

jquery.min.js

jquery.min.js

522 ms

jquery-migrate.min.js

jquery-migrate.min.js

430 ms

cookie-law-info-public.js

cookie-law-info-public.js

431 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

431 ms

add-to-cart.min.js

add-to-cart.min.js

522 ms

js.cookie.min.js

js.cookie.min.js

625 ms

woocommerce.min.js

woocommerce.min.js

626 ms

js

js

67 ms

wc-blocks.css

wc-blocks.css

625 ms

frontend.min.js

frontend.min.js

626 ms

mobile-cart.min.js

mobile-cart.min.js

628 ms

add-to-cart-quantity-btn.min.js

add-to-cart-quantity-btn.min.js

628 ms

public.js

public.js

644 ms

sourcebuster.min.js

sourcebuster.min.js

645 ms

order-attribution.min.js

order-attribution.min.js

645 ms

gdpr-donotsell.js

gdpr-donotsell.js

648 ms

site_main.js

site_main.js

733 ms

awdr-dynamic-price.js

awdr-dynamic-price.js

732 ms

spectra-block-positioning.min.js

spectra-block-positioning.min.js

737 ms

uagb-button-child.min.js

uagb-button-child.min.js

735 ms

spectra-counter.min.js

spectra-counter.min.js

737 ms

countUp.min.js

countUp.min.js

750 ms

uag-js-107290.js

uag-js-107290.js

837 ms

jquery.flexslider.min.js

jquery.flexslider.min.js

838 ms

astra-addon-65ce68338b3605-45893115.js

astra-addon-65ce68338b3605-45893115.js

841 ms

single-product-ajax-cart.min.js

single-product-ajax-cart.min.js

842 ms

cart-fragments.min.js

cart-fragments.min.js

852 ms

lepigen-logo-03-168x54.png

lepigen-logo-03-168x54.png

313 ms

viktresan-med-lepigen.jpeg

viktresan-med-lepigen.jpeg

606 ms

lepigen-superstrong-bantningspiller.png

lepigen-superstrong-bantningspiller.png

710 ms

trustpilot-lepigen.jpg

trustpilot-lepigen.jpg

507 ms

Aftonbladet_logo.png

Aftonbladet_logo.png

403 ms

expressen.logo_.png

expressen.logo_.png

509 ms

quote-free-img.png

quote-free-img.png

418 ms

effektiv-viktminskning-lepigen.jpg

effektiv-viktminskning-lepigen.jpg

833 ms

lepigen.se

lepigen.se

1162 ms

woocommerce-smallscreen-grid.min.css

woocommerce-smallscreen-grid.min.css

109 ms

Accessibility Review

lepigen.se accessibility score

95

Accessibility Issues

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.

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

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

SEO Factors

lepigen.se SEO score

97

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    SV

  • Language Claimed

    SV

  • Encoding

    UTF-8

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

lepigen.se

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