Tools & Wizards About Us
horice.org screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 98

    Accessibility

    Visual factors better than
    that of 94% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 91

    SEO

    Google-friendlier than
    70% of websites

horice.org

Hořice: Titulní stránka

Page Load Speed

6.7 sec in total

First Response

350 ms

Resources Loaded

4 sec

Page Rendered

2.4 sec

horice.org screenshot

About Website

Welcome to horice.org homepage info - get ready to check Horice best content for Czech Republic right away, or after learning these important things about horice.org

Oficiální webové stránky města Hořice

Visit horice.org

Key Findings

We analyzed Horice.org page load time and found that the first response time was 350 ms and then it took 6.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

horice.org performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.1 s

46/100

10%

LCP (Largest Contentful Paint)

Value3.8 s

55/100

25%

SI (Speed Index)

Value18.5 s

0/100

10%

TBT (Total Blocking Time)

Value6,220 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.021

100/100

15%

TTI (Time to Interactive)

Value35.8 s

0/100

10%

Network Requests Diagram

horice.org

350 ms

horice.org

911 ms

zakladni.css

306 ms

screen.css

512 ms

css2

34 ms

Our browser made a total of 83 requests to load all elements on the main page. We found that 55% of them (46 requests) were addressed to the original Horice.org, 11% (9 requests) were made to Fonts.gstatic.com and 10% (8 requests) were made to Youtube.com. The less responsive or slowest element that took the longest time to load (2.2 sec) belongs to the original domain Horice.org.

Page Optimization Overview & Recommendations

Page size can be reduced by 210.8 kB (7%)

Content Size

3.0 MB

After Optimization

2.8 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Horice.org main page is 3.0 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 2.6 MB which makes up the majority of the site volume.

HTML Optimization

-75%

Potential reduce by 54.2 kB

  • Original 71.8 kB
  • After minification 70.0 kB
  • After compression 17.6 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 54.2 kB or 75% of the original size.

Image Optimization

-2%

Potential reduce by 48.8 kB

  • Original 2.6 MB
  • After minification 2.5 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. Horice images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 45.6 kB

  • Original 251.4 kB
  • After minification 249.1 kB
  • After compression 205.7 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 45.6 kB or 18% of the original size.

CSS Optimization

-45%

Potential reduce by 62.2 kB

  • Original 138.5 kB
  • After minification 138.3 kB
  • After compression 76.3 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. Horice.org needs all CSS files to be minified and compressed as it can save up to 62.2 kB or 45% of the original size.

Requests Breakdown

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

Requests Now

71

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

horice.org

horice.org

350 ms

horice.org

horice.org

911 ms

zakladni.css

zakladni.css

306 ms

screen.css

screen.css

512 ms

css2

css2

34 ms

DuplicateScriptsVerifier.js

DuplicateScriptsVerifier.js

435 ms

js

js

64 ms

brand

brand

21 ms

brandjs.js

brandjs.js

19 ms

voliviewer_light_noCSS.js

voliviewer_light_noCSS.js

507 ms

tabs_2021.js

tabs_2021.js

228 ms

blender.js

blender.js

506 ms

volgte.js

volgte.js

506 ms

element.js

element.js

46 ms

smooth-scroll.min.js

smooth-scroll.min.js

506 ms

ma11yc.js

ma11yc.js

525 ms

znak.svg

znak.svg

192 ms

icon-facebook.svg

icon-facebook.svg

193 ms

icon-instagram-rgb.svg

icon-instagram-rgb.svg

646 ms

icon-youtube.svg

icon-youtube.svg

191 ms

lupa.svg

lupa.svg

190 ms

logo-ic.png

logo-ic.png

318 ms

Image.ashx

Image.ashx

1140 ms

Image.ashx

Image.ashx

1338 ms

Image.ashx

Image.ashx

1691 ms

Image.ashx

Image.ashx

1142 ms

Image.ashx

Image.ashx

1210 ms

Image.ashx

Image.ashx

1142 ms

Image.ashx

Image.ashx

1337 ms

Image.ashx

Image.ashx

1809 ms

Image.ashx

Image.ashx

2193 ms

Image.ashx

Image.ashx

1698 ms

Image.ashx

Image.ashx

1805 ms

Image.ashx

Image.ashx

1809 ms

Image.ashx

Image.ashx

1805 ms

Image.ashx

Image.ashx

1808 ms

Image.ashx

Image.ashx

1918 ms

Image.ashx

Image.ashx

1918 ms

znak-strzegom.png

znak-strzegom.png

1919 ms

znak-kerepes.svg

znak-kerepes.svg

2012 ms

znak-trstena.png

znak-trstena.png

1919 ms

znak-jablonka.png

znak-jablonka.png

2010 ms

OjANXQQyxBc

OjANXQQyxBc

252 ms

t1NcmEys_IA

t1NcmEys_IA

573 ms

eL2z2TzxyAg

eL2z2TzxyAg

865 ms

IZt8eyeoVpA

IZt8eyeoVpA

765 ms

blender-shadow-top.png

blender-shadow-top.png

1931 ms

blender-shadow-bottom.png

blender-shadow-bottom.png

1933 ms

Image.ashx

Image.ashx

2113 ms

mesa.svg

mesa.svg

2108 ms

card-shadow.png

card-shadow.png

2110 ms

js

js

163 ms

analytics.js

analytics.js

96 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshRTA.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDLshRTA.woff

112 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhRTA.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDIkhRTA.woff

123 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhRTA.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDOUhRTA.woff

206 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmRTA.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDGUmRTA.woff

207 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmRTA.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDFwmRTA.woff

208 ms

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImRTA.woff

XRXI3I6Li01BKofiOc5wtlZ2di8HDBImRTA.woff

208 ms

HTxpL2g2KjCFj4x8WI6ArIU.woff

HTxpL2g2KjCFj4x8WI6ArIU.woff

208 ms

HTML5PlayerPreparer.min.js

HTML5PlayerPreparer.min.js

1993 ms

api.js

api.js

61 ms

GRecaptchaGetEmail.js

GRecaptchaGetEmail.js

1993 ms

warningByBrowser.min.js

warningByBrowser.min.js

1995 ms

collect

collect

95 ms

www-player.css

www-player.css

44 ms

www-embed-player.js

www-embed-player.js

62 ms

base.js

base.js

94 ms

ad_status.js

ad_status.js

558 ms

vD-PFjxSijoP4-I0oY5JcElr_81RPxK9SqvIhUi9qS8.js

vD-PFjxSijoP4-I0oY5JcElr_81RPxK9SqvIhUi9qS8.js

434 ms

embed.js

embed.js

385 ms

id

id

72 ms

Create

Create

481 ms

Create

Create

483 ms

Create

Create

485 ms

Create

Create

596 ms

KFOmCnqEu92Fr1Mu4mxM.woff

KFOmCnqEu92Fr1Mu4mxM.woff

38 ms

KFOlCnqEu92Fr1MmEU9fBBc-.woff

KFOlCnqEu92Fr1MmEU9fBBc-.woff

37 ms

GenerateIT

GenerateIT

297 ms

GenerateIT

GenerateIT

295 ms

GenerateIT

GenerateIT

124 ms

GenerateIT

GenerateIT

32 ms

tisk.css

tisk.css

105 ms

Accessibility Review

horice.org accessibility score

98

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

Best Practices

horice.org best practices score

83

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

Page has valid source maps

SEO Factors

horice.org SEO score

91

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Page is blocked from indexing

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

High

Tap targets are not sized appropriately

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 Horice.org 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 Horice.org 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

horice.org

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