Report Summary

  • 74

    Performance

    Renders faster than
    83% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 89

    SEO

    Google-friendlier than
    66% of websites

playbuild.in

PlayBuild - Farming, Cooking and Building eco-friendly structures

Page Load Speed

2.8 sec in total

First Response

230 ms

Resources Loaded

2.3 sec

Page Rendered

261 ms

playbuild.in screenshot

About Website

Welcome to playbuild.in homepage info - get ready to check Play Build best content right away, or after learning these important things about playbuild.in

PlayBuild is a showcase of Andy's(Raghuvir) venture that involve Farming, Cooking and Building eco-friendly structures

Visit playbuild.in

Key Findings

We analyzed Playbuild.in page load time and found that the first response time was 230 ms and then it took 2.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

playbuild.in performance score

74

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

66/100

10%

LCP (Largest Contentful Paint)

Value5.1 s

25/100

25%

SI (Speed Index)

Value3.1 s

93/100

10%

TBT (Total Blocking Time)

Value90 ms

99/100

30%

CLS (Cumulative Layout Shift)

Value0.059

98/100

15%

TTI (Time to Interactive)

Value5.0 s

77/100

10%

Network Requests Diagram

playbuild.in

230 ms

playbuild.in

541 ms

jquery.flexslider-min.js

227 ms

functions.js

228 ms

jquery-1.8.0.min.js

363 ms

Our browser made a total of 34 requests to load all elements on the main page. We found that 76% of them (26 requests) were addressed to the original Playbuild.in, 6% (2 requests) were made to Fonts.googleapis.com and 6% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (696 ms) belongs to the original domain Playbuild.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 36.9 kB (5%)

Content Size

691.5 kB

After Optimization

654.6 kB

In fact, the total size of Playbuild.in main page is 691.5 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. 20% of websites need less resources to load. Images take 597.4 kB which makes up the majority of the site volume.

HTML Optimization

-67%

Potential reduce by 7.5 kB

  • Original 11.3 kB
  • After minification 10.6 kB
  • After compression 3.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 7.5 kB or 67% of the original size.

Image Optimization

-2%

Potential reduce by 11.7 kB

  • Original 597.4 kB
  • After minification 585.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. Play Build images are well optimized though.

JavaScript Optimization

-15%

Potential reduce by 10.4 kB

  • Original 70.4 kB
  • After minification 70.4 kB
  • After compression 60.0 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 10.4 kB or 15% of the original size.

CSS Optimization

-59%

Potential reduce by 7.3 kB

  • Original 12.4 kB
  • After minification 10.7 kB
  • After compression 5.1 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. Playbuild.in needs all CSS files to be minified and compressed as it can save up to 7.3 kB or 59% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (39%)

Requests Now

28

After Optimization

17

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

Accessibility Review

playbuild.in accessibility score

66

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

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

playbuild.in best practices score

50

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

Browser errors were logged to the console

High

Issues were logged in the Issues panel in Chrome Devtools

SEO Factors

playbuild.in SEO score

89

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

    N/A

  • Encoding

    WINDOWS-1252

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Playbuild.in can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Playbuild.in main page’s claimed encoding is windows-1252. 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 Play Build. 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: