Tools & Wizards About Us
frymburk.info screenshot

Report Summary

  • 49

    Performance

    Renders faster than
    67% of other websites

  • 90

    Accessibility

    Visual factors better than
    that of 74% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

frymburk.info

Městys Frymburk - Oficiální stránka městyse Frymburk

Page Load Speed

6 sec in total

First Response

455 ms

Resources Loaded

5 sec

Page Rendered

604 ms

frymburk.info screenshot

About Website

Welcome to frymburk.info homepage info - get ready to check Frymburk best content right away, or after learning these important things about frymburk.info

Oficiální stránky obce

Visit frymburk.info

Key Findings

We analyzed Frymburk.info page load time and found that the first response time was 455 ms and then it took 5.6 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

frymburk.info performance score

49

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.6 s

2/100

10%

LCP (Largest Contentful Paint)

Value7.9 s

3/100

25%

SI (Speed Index)

Value7.9 s

23/100

10%

TBT (Total Blocking Time)

Value60 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.166

71/100

15%

TTI (Time to Interactive)

Value7.5 s

47/100

10%

Network Requests Diagram

frymburk.info

455 ms

frymburk.info

543 ms

www.frymburk.info

1171 ms

style.css

349 ms

highslide.css

336 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 81% of them (42 requests) were addressed to the original Frymburk.info, 6% (3 requests) were made to Cdnjs.cloudflare.com and 6% (3 requests) were made to Static.gc-system.cz. The less responsive or slowest element that took the longest time to load (2.1 sec) relates to the external source Static.gc-system.cz.

Page Optimization Overview & Recommendations

Page size can be reduced by 95.5 kB (75%)

Content Size

127.4 kB

After Optimization

31.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Frymburk.info main page is 127.4 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. HTML takes 120.3 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 95.0 kB

  • Original 120.3 kB
  • After minification 95.1 kB
  • After compression 25.3 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 25.2 kB, which is 21% 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 95.0 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 4.0 kB
  • After minification 4.0 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. Frymburk images are well optimized though.

JavaScript Optimization

-17%

Potential reduce by 408 B

  • Original 2.4 kB
  • After minification 2.4 kB
  • After compression 2.0 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 408 B or 17% of the original size.

CSS Optimization

-20%

Potential reduce by 156 B

  • Original 796 B
  • After minification 768 B
  • After compression 640 B

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. Frymburk.info needs all CSS files to be minified and compressed as it can save up to 156 B or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 19 (44%)

Requests Now

43

After Optimization

24

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

frymburk.info

frymburk.info

455 ms

frymburk.info

frymburk.info

543 ms

www.frymburk.info

www.frymburk.info

1171 ms

style.css

style.css

349 ms

highslide.css

highslide.css

336 ms

swiper.4.5.0.min.css

swiper.4.5.0.min.css

335 ms

jquery.mmenu.all.css

jquery.mmenu.all.css

33 ms

jquery.mhead.css

jquery.mhead.css

337 ms

cookies_consent.js

cookies_consent.js

336 ms

funkce.js

funkce.js

337 ms

highslide-full.packed.js

highslide-full.packed.js

559 ms

highslide.cfg.js.php

highslide.cfg.js.php

613 ms

swiper.4.5.0.min.js

swiper.4.5.0.min.js

569 ms

jquery.min.js

jquery.min.js

573 ms

jquery.migrate.min.js

jquery.migrate.min.js

450 ms

calendarFunc.js

calendarFunc.js

459 ms

calendarHandleByKey.js

calendarHandleByKey.js

563 ms

scripts.min.js

scripts.min.js

571 ms

swiperInit.js

swiperInit.js

671 ms

popper.min.js

popper.min.js

38 ms

bootstrap.min.js

bootstrap.min.js

40 ms

jquery.mmenu.all.js

jquery.mmenu.all.js

39 ms

jquery.mhead.js

jquery.mhead.js

680 ms

css

css

33 ms

bg.png

bg.png

162 ms

crest.png

crest.png

162 ms

slideshow.jpg

slideshow.jpg

334 ms

editor-1-114-cs_1.jpg

editor-1-114-cs_1.jpg

224 ms

editor-1-140-cs_1.jpg

editor-1-140-cs_1.jpg

224 ms

evt_image.php

evt_image.php

391 ms

editor-1-141-cs_1.png

editor-1-141-cs_1.png

332 ms

mini11cs_2.jpg

mini11cs_2.jpg

226 ms

mini13cs_1.jpg

mini13cs_1.jpg

337 ms

mini12cs_1.png

mini12cs_1.png

340 ms

textcs2_1.png

textcs2_1.png

339 ms

logo_gc.svg

logo_gc.svg

444 ms

1.png

1.png

415 ms

2.png

2.png

419 ms

3.png

3.png

420 ms

4.png

4.png

421 ms

5.png

5.png

472 ms

6.png

6.png

523 ms

vlnky2.png

vlnky2.png

524 ms

bg_hc.jpg

bg_hc.jpg

863 ms

uK_94ruaZus72n54Kjc.ttf

uK_94ruaZus72n54Kjc.ttf

51 ms

uK_w4ruaZus72nbNDyceGv8.ttf

uK_w4ruaZus72nbNDyceGv8.ttf

126 ms

fa-regular-400.woff

fa-regular-400.woff

1291 ms

fa-light-300.woff

fa-light-300.woff

1517 ms

fa-solid-900.woff

fa-solid-900.woff

2062 ms

rounded-white.png

rounded-white.png

113 ms

zoomout.cur

zoomout.cur

113 ms

loader.white.gif

loader.white.gif

112 ms

Accessibility Review

frymburk.info accessibility score

90

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

Buttons do not have an accessible name

High

Links do not have a discernible name

Best Practices

frymburk.info best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

frymburk.info SEO score

92

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

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

    CS

  • Language Claimed

    CS

  • Encoding

    UTF-8

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

frymburk.info

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