Report Summary

  • 64

    Performance

    Renders faster than
    78% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 46% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 66

    SEO

    Google-friendlier than
    25% of websites

pelikan.ee

Форум клуба PELIKAN - Главная страница

Page Load Speed

8 sec in total

First Response

711 ms

Resources Loaded

7.1 sec

Page Rendered

221 ms

pelikan.ee screenshot

About Website

Click here to check amazing PELIKAN content for Estonia. Otherwise, check out these important facts you probably never knew about pelikan.ee

Клуб рыболовов PELIKAN рад приветствовать Вас на нашем сайте! Клуб зарегистрирован 8 февраля 2010г. в результате общего решения cоучредителей – людей, которым нравится проводить своё время и отдых на ...

Visit pelikan.ee

Key Findings

We analyzed Pelikan.ee page load time and found that the first response time was 711 ms and then it took 7.3 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

pelikan.ee performance score

64

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.2 s

78/100

10%

LCP (Largest Contentful Paint)

Value2.2 s

95/100

25%

SI (Speed Index)

Value5.7 s

52/100

10%

TBT (Total Blocking Time)

Value710 ms

42/100

30%

CLS (Cumulative Layout Shift)

Value0.147

77/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

Network Requests Diagram

pelikan.ee

711 ms

wp-emoji-release.min.js

370 ms

thickbox.css

235 ms

dashicons.min.css

467 ms

weptile-image-slider-widget.css

238 ms

Our browser made a total of 211 requests to load all elements on the main page. We found that 86% of them (182 requests) were addressed to the original Pelikan.ee, 2% (5 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Platform.twitter.com. The less responsive or slowest element that took the longest time to load (1.5 sec) belongs to the original domain Pelikan.ee.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (9%)

Content Size

11.1 MB

After Optimization

10.1 MB

In fact, the total size of Pelikan.ee main page is 11.1 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. 85% 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 10.0 MB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 116.3 kB

  • Original 144.1 kB
  • After minification 136.9 kB
  • After compression 27.8 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 116.3 kB or 81% of the original size.

Image Optimization

-2%

Potential reduce by 158.6 kB

  • Original 10.0 MB
  • After minification 9.8 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. PELIKAN images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 403.2 kB

  • Original 588.3 kB
  • After minification 517.0 kB
  • After compression 185.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 403.2 kB or 69% of the original size.

CSS Optimization

-82%

Potential reduce by 348.7 kB

  • Original 427.1 kB
  • After minification 338.9 kB
  • After compression 78.4 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. Pelikan.ee needs all CSS files to be minified and compressed as it can save up to 348.7 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 61 (30%)

Requests Now

204

After Optimization

143

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

Accessibility Review

pelikan.ee accessibility score

78

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

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[role]s are not contained by their required parent element

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

Tables and lists

These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.

Impact

Issue

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

pelikan.ee best practices score

67

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

High

Browser errors were logged to the console

SEO Factors

pelikan.ee SEO score

66

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

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 doesn't use legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    RU

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

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