19.1 sec in total
8.5 sec
10.4 sec
279 ms
Visit lloret.de now to see the best up-to-date LLORET content and also check out these interesting facts you probably never knew about lloret.de
Lloret.de - das Nr.1 Forum für alle
Visit lloret.deWe analyzed Lloret.de page load time and found that the first response time was 8.5 sec and then it took 10.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
lloret.de performance score
name
value
score
weighting
Value4.9 s
10/100
10%
Value6.9 s
6/100
25%
Value7.0 s
33/100
10%
Value550 ms
53/100
30%
Value0.202
61/100
15%
Value9.4 s
31/100
10%
8459 ms
96 ms
175 ms
274 ms
7 ms
Our browser made a total of 67 requests to load all elements on the main page. We found that 52% of them (35 requests) were addressed to the original Lloret.de, 13% (9 requests) were made to Pagead2.googlesyndication.com and 9% (6 requests) were made to Googleads.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (8.5 sec) belongs to the original domain Lloret.de.
Page size can be reduced by 455.3 kB (52%)
877.6 kB
422.4 kB
In fact, the total size of Lloret.de main page is 877.6 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. Javascripts take 664.0 kB which makes up the majority of the site volume.
Potential reduce by 59.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 8.1 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 59.9 kB or 85% of the original size.
Potential reduce by 5.7 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. LLORET images are well optimized though.
Potential reduce by 374.9 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 374.9 kB or 56% of the original size.
Potential reduce by 14.7 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. Lloret.de needs all CSS files to be minified and compressed as it can save up to 14.7 kB or 84% of the original size.
Number of requests can be reduced by 45 (74%)
61
16
The browser has sent 61 CSS, Javascripts, AJAX and image requests in order to completely render the main page of LLORET. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 16 to 1 for JavaScripts and as a result speed up the page load time.
index.php
8459 ms
script.js
96 ms
style.css
175 ms
sha1.js
274 ms
show_ads.js
7 ms
conversion.js
14 ms
analytics.js
8 ms
catbg.jpg
204 ms
lloret-Logo2.jpg
382 ms
titlebg.jpg
91 ms
upshrink.gif
292 ms
filter.gif
511 ms
collapse.gif
394 ms
sbox_refresh.gif
510 ms
off.gif
593 ms
xx.gif
381 ms
calendar.gif
488 ms
info.gif
488 ms
online.gif
544 ms
login.gif
567 ms
powered-mysql.gif
619 ms
powered-php.gif
666 ms
valid-xhtml10.gif
718 ms
valid-css.gif
768 ms
collect
10 ms
maintab_first.gif
562 ms
maintab_active_first.gif
593 ms
maintab_active_back.gif
625 ms
maintab_active_last.gif
659 ms
maintab_back.gif
691 ms
maintab_last.gif
724 ms
ca-pub-0105668317991702.js
45 ms
zrt_lookup.html
38 ms
show_ads_impl.js
43 ms
sboxDB.php
875 ms
52 ms
ads
153 ms
osd.js
17 ms
46 ms
ads
205 ms
gen_204
13 ms
ad
49 ms
m_window_focus_non_hydra.js
25 ms
osd_listener.js
27 ms
m_qs_click_protection.js
28 ms
728x90.jpg
58 ms
abg.js
14 ms
lidar.js
32 ms
d5qAyLYU.js
7 ms
9im3l02I.html
36 ms
pixel
70 ms
cookie_push.html
39 ms
transparent.png
25 ms
T8Ys39_ecZUP0z5o0qwgiftCx6c5Z_CDv350QIo51NY.js
13 ms
usermatchredir
48 ms
pixel
22 ms
pixel
28 ms
usermatchredir
11 ms
pixel
13 ms
sync
11 ms
style.css
91 ms
icon_biggrin.gif
123 ms
icon_surprised.gif
90 ms
icon_cool.gif
91 ms
glasses9.gif
139 ms
icon_wink.gif
188 ms
print.css
90 ms
lloret.de accessibility score
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
Buttons do not have an accessible name
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
Heading elements are not in a sequentially-descending order
lloret.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
lloret.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
Document uses legible font sizes
DE
N/A
ISO-8859-1
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lloret.de can be misinterpreted by Google and other search engines. Our service has detected that German 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 Lloret.de main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
lloret.de
Open Graph description is not detected on the main page of LLORET. 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: