Tools & Wizards About Us
penguinhouse.lv screenshot

Report Summary

  • 50

    Performance

    Renders faster than
    68% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

penguinhouse.lv

Par Projektu » PenguinHouse

Page Load Speed

4 sec in total

First Response

440 ms

Resources Loaded

3.5 sec

Page Rendered

121 ms

penguinhouse.lv screenshot

About Website

Welcome to penguinhouse.lv homepage info - get ready to check Penguin House best content right away, or after learning these important things about penguinhouse.lv

Projekta Penguin House mērķi: 1) panākt privāto, pašvaldības, valsts, sabiedrisko organizāciju un citu labprātīgo ziedotāju līdzekļu piesaisti pingvīnu mājas un pastāvīgās ekspozīcijas izveidei Rīgas ...

Visit penguinhouse.lv

Key Findings

We analyzed Penguinhouse.lv page load time and found that the first response time was 440 ms and then it took 3.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

penguinhouse.lv performance score

50

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

32/100

10%

LCP (Largest Contentful Paint)

Value3.6 s

61/100

25%

SI (Speed Index)

Value8.9 s

15/100

10%

TBT (Total Blocking Time)

Value630 ms

47/100

30%

CLS (Cumulative Layout Shift)

Value0.025

100/100

15%

TTI (Time to Interactive)

Value15.4 s

7/100

10%

Network Requests Diagram

penguinhouse.lv

440 ms

128 ms

par-projektu

133 ms

style.css

112 ms

highslide.css

222 ms

Our browser made a total of 81 requests to load all elements on the main page. We found that 20% of them (16 requests) were addressed to the original Penguinhouse.lv, 22% (18 requests) were made to Platform.twitter.com and 21% (17 requests) were made to Ifrype.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Ifrype.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 60.0 kB (6%)

Content Size

931.9 kB

After Optimization

871.9 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Penguinhouse.lv main page is 931.9 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. 70% of websites need less resources to load. Javascripts take 595.6 kB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 9.5 kB

  • Original 13.7 kB
  • After minification 13.5 kB
  • After compression 4.2 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 9.5 kB or 70% of the original size.

Image Optimization

-9%

Potential reduce by 19.8 kB

  • Original 215.7 kB
  • After minification 196.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. Penguin House images are well optimized though.

JavaScript Optimization

-3%

Potential reduce by 16.4 kB

  • Original 595.6 kB
  • After minification 595.6 kB
  • After compression 579.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. This website has mostly compressed JavaScripts.

CSS Optimization

-13%

Potential reduce by 14.3 kB

  • Original 106.8 kB
  • After minification 106.8 kB
  • After compression 92.5 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. Penguinhouse.lv needs all CSS files to be minified and compressed as it can save up to 14.3 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 41 (53%)

Requests Now

77

After Optimization

36

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 77 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Penguin House. 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 6 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

penguinhouse.lv

penguinhouse.lv

440 ms

128 ms

par-projektu

par-projektu

133 ms

style.css

style.css

112 ms

highslide.css

highslide.css

222 ms

jquery-1.7.2.min.js

jquery-1.7.2.min.js

347 ms

highslide-with-gallery.packed.js

highslide-with-gallery.packed.js

338 ms

script.js

script.js

224 ms

327 ms

es-esmu-par-pingviniem.jpg

es-esmu-par-pingviniem.jpg

254 ms

share.jpg

share.jpg

250 ms

bilde.jpg

bilde.jpg

255 ms

bilde2.jpg

bilde2.jpg

336 ms

bilde3.jpg

bilde3.jpg

119 ms

widgets.js

widgets.js

51 ms

likebox.php

likebox.php

175 ms

ga.js

ga.js

16 ms

__utm.gif

__utm.gif

12 ms

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

widget_iframe.2f70fb173b9000da126c79afe2098f02.html

128 ms

pfs3shRYZOH.css

pfs3shRYZOH.css

28 ms

DaPJf3IFK7Z.js

DaPJf3IFK7Z.js

35 ms

Y4zFOWmUObv.js

Y4zFOWmUObv.js

61 ms

xj_QemyOmNF.js

xj_QemyOmNF.js

62 ms

HbT8HXdZYIC.js

HbT8HXdZYIC.js

67 ms

CpxPwmyFdRH.js

CpxPwmyFdRH.js

65 ms

wlCZDe_a_C9.js

wlCZDe_a_C9.js

65 ms

p55HfXW__mM.js

p55HfXW__mM.js

68 ms

settings

settings

115 ms

309426193_466271242194602_3155580541055515219_n.jpg

309426193_466271242194602_3155580541055515219_n.jpg

106 ms

KhKsA6f4rG5.js

KhKsA6f4rG5.js

14 ms

309435783_466271238861269_8182450866004946009_n.jpg

309435783_466271238861269_8182450866004946009_n.jpg

100 ms

UXtr_j2Fwe-.png

UXtr_j2Fwe-.png

12 ms

new.rel.css

new.rel.css

416 ms

other.rel.css

other.rel.css

522 ms

fans.css

fans.css

616 ms

xGlobal.js

xGlobal.js

718 ms

base.js

base.js

721 ms

common.rel.js

common.rel.js

921 ms

icons.rel.js

icons.rel.js

819 ms

t.rel.js

t.rel.js

733 ms

struct.rel.js

struct.rel.js

825 ms

say.rel.js

say.rel.js

1025 ms

331fb94903.js

331fb94903.js

831 ms

timeline.e108540dddc96e4b707f5cf259a582d7.js

timeline.e108540dddc96e4b707f5cf259a582d7.js

19 ms

PenguinHouse_LV

PenguinHouse_LV

64 ms

polyfills-a40ef1678bae11e696dba45124eadd70.js

polyfills-a40ef1678bae11e696dba45124eadd70.js

19 ms

runtime-b1c52fd0a13ead5fcf6b.js

runtime-b1c52fd0a13ead5fcf6b.js

37 ms

modules-96ebc7ac3ad66d681a3d.js

modules-96ebc7ac3ad66d681a3d.js

56 ms

main-babd9234dc048fb47339.js

main-babd9234dc048fb47339.js

73 ms

_app-a9c9f1a99e4414675fb1.js

_app-a9c9f1a99e4414675fb1.js

93 ms

%5BscreenName%5D-0517bdda27d5006a5a2d.js

%5BscreenName%5D-0517bdda27d5006a5a2d.js

97 ms

_buildManifest.js

_buildManifest.js

109 ms

_ssgManifest.js

_ssgManifest.js

109 ms

8526.0c32a8f0cfc5749221a3.js

8526.0c32a8f0cfc5749221a3.js

18 ms

1755.07a49c40b12af4f75780.js

1755.07a49c40b12af4f75780.js

22 ms

8283.f3e5048cca7cef5eed7f.js

8283.f3e5048cca7cef5eed7f.js

20 ms

3077.44bfeb00af01bc4020f6.js

3077.44bfeb00af01bc4020f6.js

42 ms

1362.42d432e02f7980bca032.js

1362.42d432e02f7980bca032.js

37 ms

4956.c4e51ef593974b9db0bb.js

4956.c4e51ef593974b9db0bb.js

74 ms

5893.d500bd2a89ded806aa73.js

5893.d500bd2a89ded806aa73.js

23 ms

i_13357307.jpg

i_13357307.jpg

206 ms

i_4540528.jpg

i_4540528.jpg

206 ms

i_2955189.jpg

i_2955189.jpg

238 ms

i_3648374.jpg

i_3648374.jpg

204 ms

i_1345701.jpg

i_1345701.jpg

203 ms

i_1353616.jpg

i_1353616.jpg

336 ms

i_168622.jpg

i_168622.jpg

205 ms

top_bg.png

top_bg.png

102 ms

logo.png

logo.png

101 ms

i_3.png

i_3.png

102 ms

footer_bg.png

footer_bg.png

102 ms

i_4920229.jpg

i_4920229.jpg

352 ms

i_427919.jpg

i_427919.jpg

435 ms

i_912714.jpg

i_912714.jpg

301 ms

i_4026174.jpg

i_4026174.jpg

401 ms

i_560787.jpg

i_560787.jpg

302 ms

button.png

button.png

100 ms

followLogo.png

followLogo.png

101 ms

rounded-white.png

rounded-white.png

112 ms

zoomout.cur

zoomout.cur

112 ms

loader.white.gif

loader.white.gif

113 ms

Accessibility Review

penguinhouse.lv accessibility score

88

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.

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

Best Practices

penguinhouse.lv best practices score

67

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

High

Missing source maps for large first-party JavaScript

SEO Factors

penguinhouse.lv SEO score

77

Search Engine Optimization Advices

Language and Encoding

  • Language Detected

    LV

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

penguinhouse.lv

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