Tools & Wizards About Us
lu2.name screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

lu2.name

Page Load Speed

6.2 sec in total

First Response

332 ms

Resources Loaded

4.3 sec

Page Rendered

1.6 sec

lu2.name screenshot

About Website

Welcome to lu2.name homepage info - get ready to check Lu 2 best content right away, or after learning these important things about lu2.name

Webdesigner žijící v Praze. Vytvářím kreativní grafické návrhy webových stránek a webových aplikací.

Visit lu2.name

Key Findings

We analyzed Lu2.name page load time and found that the first response time was 332 ms and then it took 5.8 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

lu2.name performance score

0

Network Requests Diagram

lu2.name

332 ms

www.tomasludvik.cz

666 ms

normalize.min.css

106 ms

720_grid.css

207 ms

986_grid.css

203 ms

Our browser made a total of 68 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Lu2.name, 96% (65 requests) were made to Tomasludvik.cz and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (2.4 sec) relates to the external source Tomasludvik.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 535.5 kB (8%)

Content Size

6.5 MB

After Optimization

6.0 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Lu2.name main page is 6.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. 30% of websites need less resources to load. Images take 6.4 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 20.4 kB

  • Original 24.8 kB
  • After minification 20.2 kB
  • After compression 4.4 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 4.6 kB, which is 19% 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 20.4 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 422.1 kB

  • Original 6.4 MB
  • After minification 5.9 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. Lu 2 images are well optimized though.

JavaScript Optimization

-55%

Potential reduce by 73.4 kB

  • Original 132.9 kB
  • After minification 132.4 kB
  • After compression 59.5 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 73.4 kB or 55% of the original size.

CSS Optimization

-80%

Potential reduce by 19.6 kB

  • Original 24.6 kB
  • After minification 18.1 kB
  • After compression 5.0 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. Lu2.name needs all CSS files to be minified and compressed as it can save up to 19.6 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (15%)

Requests Now

66

After Optimization

56

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 66 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lu 2. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

lu2.name

lu2.name

332 ms

www.tomasludvik.cz

www.tomasludvik.cz

666 ms

normalize.min.css

normalize.min.css

106 ms

720_grid.css

720_grid.css

207 ms

986_grid.css

986_grid.css

203 ms

1236_grid.css

1236_grid.css

521 ms

1400_grid.css

1400_grid.css

214 ms

main.css

main.css

212 ms

modernizr-2.6.2-respond-1.1.0.min.js

modernizr-2.6.2-respond-1.1.0.min.js

214 ms

jquery.min.js

jquery.min.js

406 ms

responsiveslides.min.js

responsiveslides.min.js

307 ms

default.js

default.js

315 ms

main.js

main.js

314 ms

bg.jpg

bg.jpg

417 ms

tomas-ludvik.jpg

tomas-ludvik.jpg

315 ms

skill-lector.png

skill-lector.png

102 ms

skill-ux-ui.png

skill-ux-ui.png

106 ms

skill-mobil.png

skill-mobil.png

103 ms

skill-webdesign.png

skill-webdesign.png

105 ms

bg-services-2.jpg

bg-services-2.jpg

698 ms

skill-experience.png

skill-experience.png

204 ms

skill-freelance.png

skill-freelance.png

210 ms

skill-websites.png

skill-websites.png

212 ms

skill-designs.png

skill-designs.png

302 ms

bg-jcu.png

bg-jcu.png

312 ms

ff-jcu.png

ff-jcu.png

1791 ms

bg-alza.png

bg-alza.png

807 ms

alza.png

alza.png

927 ms

bg-cardsender.jpg

bg-cardsender.jpg

736 ms

app-button.svg

app-button.svg

523 ms

cardsender-01.png

cardsender-01.png

958 ms

cardsender-02.png

cardsender-02.png

1003 ms

cardsender-03.png

cardsender-03.png

1053 ms

nlcontact-01.png

nlcontact-01.png

1007 ms

nlcontact-02.png

nlcontact-02.png

1034 ms

nlcontact-03.png

nlcontact-03.png

1169 ms

nlcontact-04.png

nlcontact-04.png

1109 ms

nlcontact-05.png

nlcontact-05.png

1117 ms

bg-egc.png

bg-egc.png

1241 ms

egroovy-01.png

egroovy-01.png

1261 ms

egroovy-02.png

egroovy-02.png

1217 ms

egroovy-03.png

egroovy-03.png

1329 ms

bg-famedia.jpg

bg-famedia.jpg

1381 ms

famedia-01.png

famedia-01.png

1432 ms

famedia-02.png

famedia-02.png

1448 ms

famedia-03.png

famedia-03.png

1482 ms

fotozbozi-01.png

fotozbozi-01.png

1630 ms

fotozbozi-02.png

fotozbozi-02.png

1602 ms

ga.js

ga.js

26 ms

fotozbozi-03.png

fotozbozi-03.png

1490 ms

__utm.gif

__utm.gif

12 ms

pfdindisplaypro-light-webfont-arial.woff

pfdindisplaypro-light-webfont-arial.woff

1573 ms

pfdindisplaypro-med-webfont-arial.woff

pfdindisplaypro-med-webfont-arial.woff

1592 ms

pfdindisplaypro-lightital-webfont.woff

pfdindisplaypro-lightital-webfont.woff

1648 ms

bg-sklenik.jpg

bg-sklenik.jpg

1611 ms

sklenik-01.png

sklenik-01.png

1734 ms

sklenik-02.png

sklenik-02.png

1672 ms

sklenik-03.png

sklenik-03.png

1599 ms

bg-intya.jpg

bg-intya.jpg

1521 ms

intya-01.png

intya-01.png

1645 ms

intya-02.png

intya-02.png

2403 ms

intya-03.png

intya-03.png

1604 ms

ceske-radiokomunikace-01.png

ceske-radiokomunikace-01.png

1508 ms

ceske-radiokomunikace-02.png

ceske-radiokomunikace-02.png

1397 ms

ceske-radiokomunikace-03.png

ceske-radiokomunikace-03.png

1318 ms

quote.png

quote.png

1250 ms

cite.svg

cite.svg

1196 ms

social-icon.png

social-icon.png

1182 ms

SEO Factors

lu2.name SEO score

0

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    CS

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Lu2.name can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else), while the claimed language is Czech. Our system also found out that Lu2.name 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

lu2.name

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