Tools & Wizards About Us
laq.sk screenshot

Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 52% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

laq.sk

LaQ stavebnice,iOTOBO magnetické hračky svet tvorivosti pre deti

Page Load Speed

17.4 sec in total

First Response

7.5 sec

Resources Loaded

9.6 sec

Page Rendered

228 ms

laq.sk screenshot

About Website

Visit laq.sk now to see the best up-to-date LaQ content and also check out these interesting facts you probably never knew about laq.sk

Výnimočne kreatívne hračky pre vnímavé deti. Stavebnice LaQ, magnetické hračky iOTOBO. Svet tvorivosti a zábavy pre chlapcov a dievčatá.

Visit laq.sk

Key Findings

We analyzed Laq.sk page load time and found that the first response time was 7.5 sec and then it took 9.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

laq.sk performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.8 s

1/100

10%

LCP (Largest Contentful Paint)

Value25.8 s

0/100

25%

SI (Speed Index)

Value37.3 s

0/100

10%

TBT (Total Blocking Time)

Value23,870 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value38.6 s

0/100

10%

Network Requests Diagram

laq.sk

7547 ms

embedia.yui.css

155 ms

embedia.css

306 ms

style.css

260 ms

likebox.css

236 ms

Our browser made a total of 77 requests to load all elements on the main page. We found that 64% of them (49 requests) were addressed to the original Laq.sk, 23% (18 requests) were made to Img.youtube.com and 3% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (7.5 sec) belongs to the original domain Laq.sk.

Page Optimization Overview & Recommendations

Page size can be reduced by 251.6 kB (35%)

Content Size

722.9 kB

After Optimization

471.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Laq.sk main page is 722.9 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 370.7 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 20.9 kB

  • Original 28.2 kB
  • After minification 27.2 kB
  • After compression 7.2 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 20.9 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 11.4 kB

  • Original 370.7 kB
  • After minification 359.3 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. LaQ images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 193.7 kB

  • Original 291.9 kB
  • After minification 276.1 kB
  • After compression 98.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 193.7 kB or 66% of the original size.

CSS Optimization

-80%

Potential reduce by 25.5 kB

  • Original 32.0 kB
  • After minification 23.9 kB
  • After compression 6.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. Laq.sk needs all CSS files to be minified and compressed as it can save up to 25.5 kB or 80% of the original size.

Requests Breakdown

Number of requests can be reduced by 40 (53%)

Requests Now

76

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

laq.sk

laq.sk

7547 ms

embedia.yui.css

embedia.yui.css

155 ms

embedia.css

embedia.css

306 ms

style.css

style.css

260 ms

likebox.css

likebox.css

236 ms

mootools.js

mootools.js

430 ms

caption.js

caption.js

351 ms

embedia.yui.js

embedia.yui.js

416 ms

embedia.js

embedia.js

368 ms

swfobject.js

swfobject.js

1212 ms

swfobject.js

swfobject.js

399 ms

mootools.likebox.js

mootools.likebox.js

461 ms

system.css

system.css

502 ms

general.css

general.css

492 ms

template.css

template.css

538 ms

black.css

black.css

538 ms

white_bg.css

white_bg.css

563 ms

all.js

all.js

271 ms

bg.jpg

bg.jpg

469 ms

default.jpg

default.jpg

82 ms

default.jpg

default.jpg

44 ms

default.jpg

default.jpg

90 ms

default.jpg

default.jpg

83 ms

default.jpg

default.jpg

82 ms

default.jpg

default.jpg

32 ms

default.jpg

default.jpg

45 ms

default.jpg

default.jpg

104 ms

default.jpg

default.jpg

86 ms

default.jpg

default.jpg

81 ms

default.jpg

default.jpg

105 ms

default.jpg

default.jpg

86 ms

default.jpg

default.jpg

133 ms

default.jpg

default.jpg

98 ms

default.jpg

default.jpg

167 ms

default.jpg

default.jpg

100 ms

default.jpg

default.jpg

119 ms

default.jpg

default.jpg

149 ms

mw_shadow_l.png

mw_shadow_l.png

170 ms

mw_shadow_r.png

mw_shadow_r.png

137 ms

mw_header_t.png

mw_header_t.png

136 ms

mw_header_t_l.png

mw_header_t_l.png

137 ms

mw_header_t_r.png

mw_header_t_r.png

166 ms

mw_header_b.png

mw_header_b.png

283 ms

mw_header_l_b.png

mw_header_l_b.png

284 ms

mw_header_r_b.png

mw_header_r_b.png

284 ms

mw_menu_cap_l.png

mw_menu_cap_l.png

292 ms

mw_menu_normal_bg.png

mw_menu_normal_bg.png

292 ms

mw_menu_cap_r.png

mw_menu_cap_r.png

372 ms

ceska.jpg

ceska.jpg

380 ms

madarska.gif

madarska.gif

384 ms

anglicka.gif

anglicka.gif

436 ms

mw_content_t.png

mw_content_t.png

416 ms

mw_content_t_l.png

mw_content_t_l.png

493 ms

mw_content_t_r.png

mw_content_t_r.png

498 ms

vnimave_hracky.png

vnimave_hracky.png

517 ms

kutaj-logo.jpg

kutaj-logo.jpg

554 ms

woow_logo.png

woow_logo.png

556 ms

awards_banner.jpg

awards_banner.jpg

568 ms

8.jpg

8.jpg

700 ms

iOTOBO-logoanglais_web.png

iOTOBO-logoanglais_web.png

606 ms

facebook-white-right.png

facebook-white-right.png

650 ms

mw_line_grey.png

mw_line_grey.png

663 ms

mw_content_b.png

mw_content_b.png

661 ms

mw_content_b_l.png

mw_content_b_l.png

666 ms

mw_content_b_r.png

mw_content_b_r.png

704 ms

mw_footer_b.png

mw_footer_b.png

747 ms

mw_footer_b_l.png

mw_footer_b_l.png

783 ms

mw_footer_b_r.png

mw_footer_b_r.png

789 ms

ga.js

ga.js

8 ms

agent.php

agent.php

516 ms

__utm.gif

__utm.gif

13 ms

like.php

like.php

170 ms

h5Lp5Et_eC4.js

h5Lp5Et_eC4.js

488 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

555 ms

54 ms

xd_arbiter.php

xd_arbiter.php

222 ms

xd_arbiter.php

xd_arbiter.php

426 ms

Accessibility Review

laq.sk accessibility score

81

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

laq.sk best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

laq.sk SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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

Language and Encoding

  • Language Detected

    SK

  • Language Claimed

    SK

  • Encoding

    UTF-8

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

laq.sk

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