Report Summary

  • 68

    Performance

    Renders faster than
    80% of other websites

  • 54

    Accessibility

    Visual factors better than
    that of 23% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 58

    SEO

    Google-friendlier than
    20% of websites

putni.info

Jāņa putni

Page Load Speed

7.9 sec in total

First Response

494 ms

Resources Loaded

5.6 sec

Page Rendered

1.8 sec

putni.info screenshot

About Website

Click here to check amazing Putni content. Otherwise, check out these important facts you probably never knew about putni.info

Visit putni.info

Key Findings

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

putni.info performance score

68

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.0 s

83/100

10%

LCP (Largest Contentful Paint)

Value2.3 s

94/100

25%

SI (Speed Index)

Value4.8 s

66/100

10%

TBT (Total Blocking Time)

Value500 ms

57/100

30%

CLS (Cumulative Layout Shift)

Value0.461

19/100

15%

TTI (Time to Interactive)

Value3.2 s

94/100

10%

Network Requests Diagram

putni.info

494 ms

prototype.js

499 ms

scriptaculous.js

173 ms

lightbox.js

279 ms

lightbox.css

191 ms

Our browser made a total of 264 requests to load all elements on the main page. We found that all of those requests were addressed to Putni.info and no external sources were called. The less responsive or slowest element that took the longest time to load (595 ms) belongs to the original domain Putni.info.

Page Optimization Overview & Recommendations

Page size can be reduced by 395.7 kB (19%)

Content Size

2.1 MB

After Optimization

1.7 MB

In fact, the total size of Putni.info main page is 2.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. 60% of websites need less resources to load. Images take 1.7 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 104.4 kB

  • Original 115.9 kB
  • After minification 115.7 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. 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 104.4 kB or 90% of the original size.

Image Optimization

-6%

Potential reduce by 100.0 kB

  • Original 1.7 MB
  • After minification 1.6 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. Putni images are well optimized though.

JavaScript Optimization

-81%

Potential reduce by 188.8 kB

  • Original 233.1 kB
  • After minification 169.9 kB
  • After compression 44.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 188.8 kB or 81% of the original size.

CSS Optimization

-72%

Potential reduce by 2.5 kB

  • Original 3.5 kB
  • After minification 2.8 kB
  • After compression 993 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. Putni.info needs all CSS files to be minified and compressed as it can save up to 2.5 kB or 72% of the original size.

Requests Breakdown

Number of requests can be reduced by 5 (2%)

Requests Now

263

After Optimization

258

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

Accessibility Review

putni.info accessibility score

54

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

putni.info best practices score

75

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

putni.info SEO score

58

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

Language and Encoding

  • Language Detected

    N/A

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Putni.info can be misinterpreted by Google and other search engines. Unfortunately we cannot identify language used on the page (probably there is a mix of languages, too little text or something else) and no language is claimed in <html> or <meta> tags either. Our system also found out that Putni.info main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

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