Tools & Wizards About Us
ptice.net screenshot

Report Summary

  • 55

    Performance

    Renders faster than
    72% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

ptice.net

ptice Hrvatske

Page Load Speed

5.9 sec in total

First Response

978 ms

Resources Loaded

4.4 sec

Page Rendered

451 ms

ptice.net screenshot

About Website

Click here to check amazing Ptice content for Croatia. Otherwise, check out these important facts you probably never knew about ptice.net

Hrvatsko društvo za zaštitu ptica i prirode i Udruga BIOM pozivaju sve promatrače ptica i ljubitelje prirode da se tijekom proljeća 2021. godine uključe u

Visit ptice.net

Key Findings

We analyzed Ptice.net page load time and found that the first response time was 978 ms and then it took 4.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

ptice.net performance score

55

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

20/100

10%

LCP (Largest Contentful Paint)

Value8.0 s

3/100

25%

SI (Speed Index)

Value6.6 s

37/100

10%

TBT (Total Blocking Time)

Value80 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

ptice.net

978 ms

www.ptice.net

1189 ms

wp-emoji-release.min.js

168 ms

wiki-embed.css

174 ms

bbpress.css

177 ms

Our browser made a total of 50 requests to load all elements on the main page. We found that 96% of them (48 requests) were addressed to the original Ptice.net, 2% (1 request) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.2 sec) belongs to the original domain Ptice.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 614.6 kB (49%)

Content Size

1.2 MB

After Optimization

628.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ptice.net main page is 1.2 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. 50% of websites need less resources to load. Javascripts take 471.0 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 60.0 kB

  • Original 71.5 kB
  • After minification 60.1 kB
  • After compression 11.5 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 11.5 kB, which is 16% 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 60.0 kB or 84% of the original size.

Image Optimization

-3%

Potential reduce by 14.4 kB

  • Original 436.6 kB
  • After minification 422.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. Ptice images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 320.9 kB

  • Original 471.0 kB
  • After minification 459.0 kB
  • After compression 150.1 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 320.9 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 219.3 kB

  • Original 264.2 kB
  • After minification 239.1 kB
  • After compression 44.9 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. Ptice.net needs all CSS files to be minified and compressed as it can save up to 219.3 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (57%)

Requests Now

44

After Optimization

19

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ptice.net

ptice.net

978 ms

www.ptice.net

www.ptice.net

1189 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

168 ms

wiki-embed.css

wiki-embed.css

174 ms

bbpress.css

bbpress.css

177 ms

light_style.css

light_style.css

179 ms

style.css

style.css

180 ms

public.css

public.css

182 ms

virtue.css

virtue.css

422 ms

default.css

default.css

345 ms

style.css

style.css

351 ms

css

css

24 ms

jquery.js

jquery.js

444 ms

jquery-migrate.min.js

jquery-migrate.min.js

357 ms

jquery-2.1.4.min.js

jquery-2.1.4.min.js

450 ms

public.js

public.js

525 ms

modernizr.min.js

modernizr.min.js

537 ms

jscripts.php

jscripts.php

540 ms

jquery.query.js

jquery.query.js

581 ms

url.min.js

url.min.js

616 ms

editor.js

editor.js

633 ms

collapse.js

collapse.js

698 ms

jquery.equalizer.js

jquery.equalizer.js

712 ms

jscripts-ftr-min.js

jscripts-ftr-min.js

713 ms

masonry.min.js

masonry.min.js

751 ms

plugins-min.js

plugins-min.js

1031 ms

main.js

main.js

815 ms

wp-embed.min.js

wp-embed.min.js

867 ms

style.css

style.css

538 ms

logo1.png

logo1.png

418 ms

nrad3160014.jpg

nrad3160014.jpg

418 ms

12768169_1028861090493891_8921572584527176677_o-365x365.jpg

12768169_1028861090493891_8921572584527176677_o-365x365.jpg

420 ms

428.jpg

428.jpg

417 ms

11080859_871710409542294_6781694800073159887_o-365x365.jpg

11080859_871710409542294_6781694800073159887_o-365x365.jpg

420 ms

DSC_0507-365x365.jpg

DSC_0507-365x365.jpg

418 ms

Ku%C4%87ica-za-ptice-u-vo%C4%87njaku-365x365.jpg

Ku%C4%87ica-za-ptice-u-vo%C4%87njaku-365x365.jpg

557 ms

Centar-za-promatranje-ptica-Nijemci-365x365.jpg

Centar-za-promatranje-ptica-Nijemci-365x365.jpg

520 ms

LEA-radionica.jpg

LEA-radionica.jpg

600 ms

Larus1-365x365.jpg

Larus1-365x365.jpg

556 ms

vransko-365x365.jpg

vransko-365x365.jpg

705 ms

nrad3160014-80x50.jpg

nrad3160014-80x50.jpg

581 ms

12768169_1028861090493891_8921572584527176677_o-80x50.jpg

12768169_1028861090493891_8921572584527176677_o-80x50.jpg

662 ms

428-80x50.jpg

428-80x50.jpg

715 ms

11080859_871710409542294_6781694800073159887_o-80x50.jpg

11080859_871710409542294_6781694800073159887_o-80x50.jpg

716 ms

DSC_0507-80x50.jpg

DSC_0507-80x50.jpg

751 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

904 ms

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

1EqTbJWOZQBfhZ0e3RL9uvesZW2xOQ-xsNqO47m55DA.ttf

356 ms

Roboto-Regular.ttf

Roboto-Regular.ttf

1095 ms

Roboto-Thin.ttf

Roboto-Thin.ttf

1206 ms

nav_arrows.png

nav_arrows.png

524 ms

Accessibility Review

ptice.net accessibility score

80

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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

Some elements have a [tabindex] value greater than 0

Best Practices

ptice.net best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

ptice.net SEO score

89

Search Engine Optimization Advices

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    HR

  • Language Claimed

    HR

  • Encoding

    UTF-8

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

ptice.net

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