Report Summary

  • 5

    Performance

    Renders faster than
    21% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

howdidyoumakethis.com

Home - How Did You Make This? | Luxe DIY

Page Load Speed

3.6 sec in total

First Response

600 ms

Resources Loaded

2.6 sec

Page Rendered

367 ms

howdidyoumakethis.com screenshot

About Website

Click here to check amazing Howdidyou Make This content for United States. Otherwise, check out these important facts you probably never knew about howdidyoumakethis.com

Visit howdidyoumakethis.com

Key Findings

We analyzed Howdidyoumakethis.com page load time and found that the first response time was 600 ms and then it took 3 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

howdidyoumakethis.com performance score

5

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.7 s

0/100

10%

LCP (Largest Contentful Paint)

Value16.0 s

0/100

25%

SI (Speed Index)

Value12.3 s

3/100

10%

TBT (Total Blocking Time)

Value1,390 ms

16/100

30%

CLS (Cumulative Layout Shift)

Value1.007

2/100

15%

TTI (Time to Interactive)

Value25.1 s

0/100

10%

Network Requests Diagram

howdidyoumakethis.com

600 ms

style.css

22 ms

css

40 ms

css

51 ms

jquery.min.js

46 ms

Our browser made a total of 86 requests to load all elements on the main page. We found that 58% of them (50 requests) were addressed to the original Howdidyoumakethis.com, 6% (5 requests) were made to Api.viglink.com and 5% (4 requests) were made to Cdn.viglink.com. The less responsive or slowest element that took the longest time to load (1 sec) relates to the external source Projectwonderful.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 640.6 kB (62%)

Content Size

1.0 MB

After Optimization

386.2 kB

In fact, the total size of Howdidyoumakethis.com main page is 1.0 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. Javascripts take 501.3 kB which makes up the majority of the site volume.

HTML Optimization

-81%

Potential reduce by 108.8 kB

  • Original 134.2 kB
  • After minification 134.1 kB
  • After compression 25.4 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 108.8 kB or 81% of the original size.

Image Optimization

-5%

Potential reduce by 5.6 kB

  • Original 101.6 kB
  • After minification 96.1 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. Howdidyou Make This images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 306.0 kB

  • Original 501.3 kB
  • After minification 501.0 kB
  • After compression 195.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 306.0 kB or 61% of the original size.

CSS Optimization

-76%

Potential reduce by 220.2 kB

  • Original 289.7 kB
  • After minification 277.7 kB
  • After compression 69.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. Howdidyoumakethis.com needs all CSS files to be minified and compressed as it can save up to 220.2 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (86%)

Requests Now

78

After Optimization

11

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

Accessibility Review

howdidyoumakethis.com accessibility score

86

Accessibility Issues

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

Image elements do not have [alt] attributes

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

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

howdidyoumakethis.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

howdidyoumakethis.com SEO score

76

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

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

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 Howdidyoumakethis.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 Howdidyoumakethis.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

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