Tools & Wizards About Us
lookylooky.de screenshot

Report Summary

  • 0

    Performance

  • 33

    Accessibility

    Visual factors better than
    that of 18% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 73

    SEO

    Google-friendlier than
    31% of websites

lookylooky.de

LookyLooky das Programm zum Erstellen digitaler Alben

Page Load Speed

1.2 sec in total

First Response

286 ms

Resources Loaded

798 ms

Page Rendered

81 ms

lookylooky.de screenshot

About Website

Visit lookylooky.de now to see the best up-to-date Looky content and also check out these interesting facts you probably never knew about lookylooky.de

Interaktive Bilder mit PAN360 fr das Album die Hompage und vieles mehr. Hier lassen sich virtuelle Rundgnge in Gebuden und Stdten realisieren.

Visit lookylooky.de

Key Findings

We analyzed Lookylooky.de page load time and found that the first response time was 286 ms and then it took 879 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

lookylooky.de performance score

0

Network Requests Diagram

lookylooky.de

286 ms

kopf.htm

104 ms

menue.htm

211 ms

seite.htm

216 ms

Metlighto.jpg

113 ms

Our browser made a total of 17 requests to load all elements on the main page. We found that all of those requests were addressed to Lookylooky.de and no external sources were called. The less responsive or slowest element that took the longest time to load (296 ms) belongs to the original domain Lookylooky.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 5.9 kB (17%)

Content Size

34.5 kB

After Optimization

28.6 kB

  • HTML
  • Images

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

HTML Optimization

-55%

Potential reduce by 581 B

  • Original 1.1 kB
  • After minification 1.0 kB
  • After compression 483 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 581 B or 55% of the original size.

Image Optimization

-16%

Potential reduce by 5.3 kB

  • Original 33.4 kB
  • After minification 28.1 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, Looky needs image optimization as it can save up to 5.3 kB or 16% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

Requests Breakdown

We found no issues to fix!

Requests Now

15

After Optimization

15

  • AJAX
  • Images

The browser has sent 15 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Looky . According to our analytics all requests are already optimized.

Network Requests Diagram

lookylooky.de

lookylooky.de

286 ms

kopf.htm

kopf.htm

104 ms

menue.htm

menue.htm

211 ms

seite.htm

seite.htm

216 ms

Metlighto.jpg

Metlighto.jpg

113 ms

LookySchrift.gif

LookySchrift.gif

207 ms

img_counter.cgi

img_counter.cgi

256 ms

Metlightl1.jpg

Metlightl1.jpg

110 ms

buttonhome.jpg

buttonhome.jpg

112 ms

buttondownload.jpg

buttondownload.jpg

114 ms

buttonthemen.jpg

buttonthemen.jpg

202 ms

buttonlizenz.jpg

buttonlizenz.jpg

207 ms

buttonkontakt.jpg

buttonkontakt.jpg

216 ms

karton4.jpg

karton4.jpg

211 ms

punkt.jpg

punkt.jpg

212 ms

linie.jpg

linie.jpg

215 ms

splashsmall.jpg

splashsmall.jpg

296 ms

Accessibility Review

lookylooky.de accessibility score

33

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

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

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

Best Practices

lookylooky.de best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

High

Browser errors were logged to the console

SEO Factors

lookylooky.de SEO score

73

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lookylooky.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 Lookylooky.de main page’s claimed encoding is . 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.

Social Sharing Optimization

lookylooky.de

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