Tools & Wizards About Us
lejola.de screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 60

    Accessibility

    Visual factors better than
    that of 26% of websites

  • 58

    Best Practices

    More advanced features
    available than in
    20% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

lejola.de

Webdesign Heidelberg | Internet Agentur Web Design Heidelberg

Page Load Speed

5.6 sec in total

First Response

264 ms

Resources Loaded

5.1 sec

Page Rendered

229 ms

lejola.de screenshot

About Website

Click here to check amazing Lejola content. Otherwise, check out these important facts you probably never knew about lejola.de

Die Internetagentur für Webdesign Heidelberg / Mannheim mit dem Fokus auf Internetanwendungen für Unternehmen.Erfahrene Webdesigner, faire Webdesign Preise und Suchmaschinenoptimierung.

Visit lejola.de

Key Findings

We analyzed Lejola.de page load time and found that the first response time was 264 ms and then it took 5.3 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

lejola.de performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.9 s

4/100

10%

LCP (Largest Contentful Paint)

Value6.9 s

6/100

25%

SI (Speed Index)

Value6.6 s

38/100

10%

TBT (Total Blocking Time)

Value330 ms

75/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value6.8 s

55/100

10%

Network Requests Diagram

lejola.de

264 ms

lejola.de

523 ms

jcemediabox.css

100 ms

style.css

197 ms

style.css

186 ms

Our browser made a total of 87 requests to load all elements on the main page. We found that 79% of them (69 requests) were addressed to the original Lejola.de, 15% (13 requests) were made to Static.xx.fbcdn.net and 2% (2 requests) were made to Ssl.google-analytics.com. The less responsive or slowest element that took the longest time to load (3.7 sec) belongs to the original domain Lejola.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 565.6 kB (60%)

Content Size

941.8 kB

After Optimization

376.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lejola.de main page is 941.8 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. 40% of websites need less resources to load. Images take 717.8 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 30.9 kB

  • Original 40.9 kB
  • After minification 37.1 kB
  • After compression 10.0 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 30.9 kB or 76% of the original size.

Image Optimization

-70%

Potential reduce by 499.2 kB

  • Original 717.8 kB
  • After minification 218.6 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. Obviously, Lejola needs image optimization as it can save up to 499.2 kB or 70% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-19%

Potential reduce by 33.6 kB

  • Original 173.8 kB
  • After minification 173.8 kB
  • After compression 140.2 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 33.6 kB or 19% of the original size.

CSS Optimization

-20%

Potential reduce by 1.9 kB

  • Original 9.3 kB
  • After minification 9.3 kB
  • After compression 7.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. Lejola.de needs all CSS files to be minified and compressed as it can save up to 1.9 kB or 20% of the original size.

Requests Breakdown

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

Requests Now

84

After Optimization

41

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

lejola.de

lejola.de

264 ms

lejola.de

lejola.de

523 ms

jcemediabox.css

jcemediabox.css

100 ms

style.css

style.css

197 ms

style.css

style.css

186 ms

nsb-opac-inv.css

nsb-opac-inv.css

279 ms

style.css

style.css

278 ms

2clicksocialbuttons.css

2clicksocialbuttons.css

281 ms

mootools-core.js

mootools-core.js

387 ms

core.js

core.js

297 ms

caption.js

caption.js

374 ms

jcemediabox.js

jcemediabox.js

474 ms

mootools-more.js

mootools-more.js

494 ms

engine.js

engine.js

361 ms

powertools-1.2.0.js

powertools-1.2.0.js

469 ms

slider.js

slider.js

487 ms

2clicksocialbuttons.js

2clicksocialbuttons.js

602 ms

system.css

system.css

612 ms

template.css

template.css

566 ms

prev.png

prev.png

93 ms

likebox.php

likebox.php

106 ms

next.png

next.png

89 ms

f_off.png

f_off.png

193 ms

t_off.png

t_off.png

195 ms

gp_off.png

gp_off.png

194 ms

info_button.png

info_button.png

194 ms

webdesign-fuer-unternehmen.png

webdesign-fuer-unternehmen.png

196 ms

socialmedia.png

socialmedia.png

296 ms

suchmaschinenoptimierung.png

suchmaschinenoptimierung.png

466 ms

kommunikationsmanagement.png

kommunikationsmanagement.png

3716 ms

kontakt.png

kontakt.png

212 ms

facebook_rou_32.png

facebook_rou_32.png

108 ms

myspace_rou_32.png

myspace_rou_32.png

207 ms

twitter_rou_32.png

twitter_rou_32.png

294 ms

digg_rou_32.png

digg_rou_32.png

305 ms

delicious_rou_32.png

delicious_rou_32.png

668 ms

stumbleupon_rou_32.png

stumbleupon_rou_32.png

394 ms

google_rou_32.png

google_rou_32.png

396 ms

reddit_rou_32.png

reddit_rou_32.png

402 ms

newsvine_rou_32.png

newsvine_rou_32.png

492 ms

technorati_rou_32.png

technorati_rou_32.png

498 ms

linkedin_rou_32.png

linkedin_rou_32.png

500 ms

mixx_rou_32.png

mixx_rou_32.png

561 ms

call-to-action-homepage.jpg

call-to-action-homepage.jpg

589 ms

facebook.png

facebook.png

598 ms

googleplus.png

googleplus.png

597 ms

xing.png

xing.png

656 ms

youtube.png

youtube.png

687 ms

twitter.png

twitter.png

696 ms

linkedin.png

linkedin.png

698 ms

empireavenue.png

empireavenue.png

752 ms

flickr.png

flickr.png

872 ms

rss.png

rss.png

784 ms

system.css

system.css

792 ms

5Sn4Pq8FsXm.css

5Sn4Pq8FsXm.css

12 ms

DaPJf3IFK7Z.js

DaPJf3IFK7Z.js

16 ms

Y4zFOWmUObv.js

Y4zFOWmUObv.js

41 ms

8O2J-mJIMh1.js

8O2J-mJIMh1.js

42 ms

QCHZeiE_shc.js

QCHZeiE_shc.js

42 ms

4aFcRp6-srT.js

4aFcRp6-srT.js

44 ms

Mgao39tvtRW.js

Mgao39tvtRW.js

46 ms

0bio7TMsDws.js

0bio7TMsDws.js

45 ms

kY8eYg-9-SS.js

kY8eYg-9-SS.js

44 ms

DJbp39Fn87q.js

DJbp39Fn87q.js

45 ms

p55HfXW__mM.js

p55HfXW__mM.js

46 ms

299974178_119416494180651_6764798254400114840_n.jpg

299974178_119416494180651_6764798254400114840_n.jpg

110 ms

298840195_119416497513984_6089785975576453127_n.jpg

298840195_119416497513984_6089785975576453127_n.jpg

168 ms

QoMTH0SpLC5.js

QoMTH0SpLC5.js

8 ms

VuRstRCPjmu.png

VuRstRCPjmu.png

7 ms

interface.png

interface.png

93 ms

call-to-action-lejola.png

call-to-action-lejola.png

100 ms

webdesign-heidelberg.jpg

webdesign-heidelberg.jpg

105 ms

loader.gif

loader.gif

187 ms

switch.png

switch.png

103 ms

c_border_tl.png

c_border_tl.png

279 ms

c_border_br.png

c_border_br.png

198 ms

ufo.jpg

ufo.jpg

201 ms

li_grau.gif

li_grau.gif

206 ms

facebook.png

facebook.png

282 ms

twitter.png

twitter.png

297 ms

xing.png

xing.png

304 ms

googleplus.png

googleplus.png

307 ms

feed.png

feed.png

484 ms

ga.js

ga.js

17 ms

popup.html

popup.html

352 ms

tooltip.html

tooltip.html

367 ms

__utm.gif

__utm.gif

10 ms

Accessibility Review

lejola.de accessibility score

60

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

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

High

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

Best Practices

lejola.de best practices score

58

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

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

lejola.de SEO score

62

Search Engine Optimization Advices

Content Best Practices

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

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

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

lejola.de

Open Graph description is not detected on the main page of Lejola. 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: