Tools & Wizards About Us
pengrees.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    56% of other websites

  • 61

    Accessibility

    Visual factors better than
    that of 27% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 88

    SEO

    Google-friendlier than
    65% of websites

pengrees.com

Tastes of Health

Page Load Speed

2.2 sec in total

First Response

46 ms

Resources Loaded

1.6 sec

Page Rendered

597 ms

pengrees.com screenshot

About Website

Welcome to pengrees.com homepage info - get ready to check Pengrees best content right away, or after learning these important things about pengrees.com

Hi, I am Agnieszka, and I am passionate about delicious but healthy food. Many healthy dishes are bland and uninteresting. I reject this. So I created my blog Tastes of Health to share my yummy...

Visit pengrees.com

Key Findings

We analyzed Pengrees.com page load time and found that the first response time was 46 ms and then it took 2.2 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 45% of websites can load faster.

Performance Metrics

pengrees.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.7 s

59/100

10%

LCP (Largest Contentful Paint)

Value9.5 s

0/100

25%

SI (Speed Index)

Value5.2 s

60/100

10%

TBT (Total Blocking Time)

Value1,170 ms

21/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value8.5 s

38/100

10%

Network Requests Diagram

pengrees.com

46 ms

tastesofhealth.tumblr.com

177 ms

pre_tumblelog.js

119 ms

index.build.css

122 ms

bilmur.min.js

122 ms

Our browser made a total of 64 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Pengrees.com, 22% (14 requests) were made to Assets.tumblr.com and 17% (11 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source 64.media.tumblr.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 101.4 kB (33%)

Content Size

310.7 kB

After Optimization

209.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Pengrees.com main page is 310.7 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. 65% of websites need less resources to load. HTML takes 122.5 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 100.0 kB

  • Original 122.5 kB
  • After minification 110.8 kB
  • After compression 22.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 100.0 kB or 82% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 45.7 kB
  • After minification 45.7 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. Pengrees images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 465 B

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

CSS Optimization

-3%

Potential reduce by 957 B

  • Original 31.9 kB
  • After minification 31.9 kB
  • After compression 30.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. Pengrees.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 32 (65%)

Requests Now

49

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

pengrees.com

pengrees.com

46 ms

tastesofhealth.tumblr.com

tastesofhealth.tumblr.com

177 ms

pre_tumblelog.js

pre_tumblelog.js

119 ms

index.build.css

index.build.css

122 ms

bilmur.min.js

bilmur.min.js

122 ms

tumblelog_post_message_queue.js

tumblelog_post_message_queue.js

121 ms

stylesheet.css

stylesheet.css

135 ms

bootstrap.min.css

bootstrap.min.css

154 ms

font-awesome.min.css

font-awesome.min.css

193 ms

css

css

126 ms

css

css

179 ms

css

css

195 ms

css

css

208 ms

delicious.css

delicious.css

147 ms

jquery.min.js

jquery.min.js

166 ms

delicious.js

delicious.js

144 ms

jquery.min.js

jquery.min.js

189 ms

jquery.initialize.js

jquery.initialize.js

150 ms

index.build.js

index.build.js

177 ms

analytics.js

analytics.js

409 ms

63a286d6a27046004cbf80c0ffc28c9726fdc5b2.png

63a286d6a27046004cbf80c0ffc28c9726fdc5b2.png

201 ms

96ed0d792793a77df73d52f352468e5affbafa0f.png

96ed0d792793a77df73d52f352468e5affbafa0f.png

1078 ms

515 ms

like_iframe.html

like_iframe.html

126 ms

512 ms

570 ms

568 ms

ac024b37c6ceb26b367f181cc195084fa1453711.png

ac024b37c6ceb26b367f181cc195084fa1453711.png

578 ms

93c6b93a7aaa8a26df902ffc8517cac1195a86f9.png

93c6b93a7aaa8a26df902ffc8517cac1195a86f9.png

888 ms

38800c722f896c12d5dcfefa10fc8903e8853ee4.png

38800c722f896c12d5dcfefa10fc8903e8853ee4.png

964 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qOK7j.woff

492 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwlxdo.woff

550 ms

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

pxiByp8kv8JHgFVrLCz7Z1xlEw.woff

561 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

237 ms

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0Coq92mg.woff

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-C0Coq92mg.woff

784 ms

font

font

900 ms

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mg.woff

0QI8MX1D_JOuMw_hLdO6T2wV9KnW-MoFoq92mg.woff

829 ms

font

font

901 ms

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqs.woff

0QI6MX1D_JOuGQbT0gvTJPa787z5vBJBkqs.woff

826 ms

font

font

898 ms

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqs.woff

0QI6MX1D_JOuGQbT0gvTJPa787weuxJBkqs.woff

899 ms

font

font

901 ms

impixu

impixu

449 ms

g.gif

g.gif

443 ms

impixu

impixu

353 ms

analytics.html

analytics.html

159 ms

login_check.html

login_check.html

74 ms

collect

collect

155 ms

g.gif

g.gif

428 ms

g.gif

g.gif

427 ms

consent

consent

116 ms

index.build.css

index.build.css

99 ms

index.build.js

index.build.js

161 ms

header.build.js

header.build.js

95 ms

exceptions.js

exceptions.js

95 ms

index.build.js

index.build.js

327 ms

beacon.js

beacon.js

378 ms

impixu

impixu

300 ms

impixu

impixu

301 ms

impixu

impixu

371 ms

impixu

impixu

371 ms

cdn.json

cdn.json

274 ms

cs.js

cs.js

124 ms

g.gif

g.gif

79 ms

Accessibility Review

pengrees.com accessibility score

61

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

High

Links do not have a discernible name

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

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

pengrees.com best practices score

83

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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

pengrees.com SEO score

88

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

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

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

pengrees.com

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