Tools & Wizards About Us
dylanjh.com screenshot

Report Summary

  • 22

    Performance

    Renders faster than
    40% of other websites

  • 68

    Accessibility

    Visual factors better than
    that of 33% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 91

    SEO

    Google-friendlier than
    71% of websites

dylanjh.com

Dylan Hunt - Shopify Liquid Coding and Shopify Script tutorials

Page Load Speed

12.9 sec in total

First Response

126 ms

Resources Loaded

3.9 sec

Page Rendered

8.9 sec

dylanjh.com screenshot

About Website

Welcome to dylanjh.com homepage info - get ready to check Dylan Jh best content for United States right away, or after learning these important things about dylanjh.com

Free Shopify Scripts, and liquid tutorials for basic and intermediate developers, including HTML, CSS, Ruby, and Javascript

Visit dylanjh.com

Key Findings

We analyzed Dylanjh.com page load time and found that the first response time was 126 ms and then it took 12.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

dylanjh.com performance score

22

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value7.1 s

1/100

10%

LCP (Largest Contentful Paint)

Value10.8 s

0/100

25%

SI (Speed Index)

Value7.1 s

31/100

10%

TBT (Total Blocking Time)

Value1,630 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.067

96/100

15%

TTI (Time to Interactive)

Value14.1 s

9/100

10%

Network Requests Diagram

dylanjh.com

126 ms

dylanjh.com

133 ms

application-de35d31f90822ffebf9b6df35b87c457e4b4701d82f869126a68dba759bd7acc.css

405 ms

application-50156b3197f50a886c6775d258970819e053d1ce0a3f481137d739432ee9c950.js

301 ms

run_prettify.js

237 ms

Our browser made a total of 44 requests to load all elements on the main page. We found that 14% of them (6 requests) were addressed to the original Dylanjh.com, 32% (14 requests) were made to Gist.github.com and 14% (6 requests) were made to Static.klaviyo.com. The less responsive or slowest element that took the longest time to load (1.7 sec) relates to the external source Cdn.shopify.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.0 MB (51%)

Content Size

2.0 MB

After Optimization

963.4 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Dylanjh.com main page is 2.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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. CSS take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 385.1 kB

  • Original 421.0 kB
  • After minification 380.0 kB
  • After compression 35.9 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 385.1 kB or 91% of the original size.

JavaScript Optimization

-61%

Potential reduce by 127.7 kB

  • Original 209.6 kB
  • After minification 209.6 kB
  • After compression 81.9 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 127.7 kB or 61% of the original size.

CSS Optimization

-38%

Potential reduce by 508.7 kB

  • Original 1.4 MB
  • After minification 1.4 MB
  • After compression 845.6 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. Dylanjh.com needs all CSS files to be minified and compressed as it can save up to 508.7 kB or 38% of the original size.

Requests Breakdown

Number of requests can be reduced by 25 (68%)

Requests Now

37

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

dylanjh.com

dylanjh.com

126 ms

dylanjh.com

dylanjh.com

133 ms

application-de35d31f90822ffebf9b6df35b87c457e4b4701d82f869126a68dba759bd7acc.css

application-de35d31f90822ffebf9b6df35b87c457e4b4701d82f869126a68dba759bd7acc.css

405 ms

application-50156b3197f50a886c6775d258970819e053d1ce0a3f481137d739432ee9c950.js

application-50156b3197f50a886c6775d258970819e053d1ce0a3f481137d739432ee9c950.js

301 ms

run_prettify.js

run_prettify.js

237 ms

cil2zcz.css

cil2zcz.css

243 ms

js

js

240 ms

klaviyo.js

klaviyo.js

318 ms

analytics.js

analytics.js

72 ms

p.css

p.css

146 ms

collect

collect

417 ms

collect

collect

543 ms

dino-5af26603708a8fb00b09a20545df909a0d27cd23699626a1649f670b68e9cbc3.png

dino-5af26603708a8fb00b09a20545df909a0d27cd23699626a1649f670b68e9cbc3.png

265 ms

Create_your_online_store_today_with_Shopify_2020-04-23_07-08-22.png

Create_your_online_store_today_with_Shopify_2020-04-23_07-08-22.png

684 ms

Oberlo_2020-04-23_07-08-40.png

Oberlo_2020-04-23_07-08-40.png

670 ms

Narrative_Theme_-_Earthy_-_Ecommerce_Website_Template_2020-04-23_07-08-56.png

Narrative_Theme_-_Earthy_-_Ecommerce_Website_Template_2020-04-23_07-08-56.png

1740 ms

d

d

283 ms

d

d

284 ms

fontawesome-webfont-ba0c59deb5450f5cb41b3f93609ee2d0d995415877ddfa223e8a8a7533474f07.woff

fontawesome-webfont-ba0c59deb5450f5cb41b3f93609ee2d0d995415877ddfa223e8a8a7533474f07.woff

283 ms

43c39e779b6e0f9faa37b0da71f4d993.json

43c39e779b6e0f9faa37b0da71f4d993.json

428 ms

0a292c697a4b5270fe3fc40ab79bbc1c.json

0a292c697a4b5270fe3fc40ab79bbc1c.json

427 ms

b4c989b6b55cc370b7d407082472dc0e.json

b4c989b6b55cc370b7d407082472dc0e.json

428 ms

b46510b2f41f2709bc3c2dc939dcc210.json

b46510b2f41f2709bc3c2dc939dcc210.json

426 ms

0ba9ef623cd31f981e12fcedf41adb56.json

0ba9ef623cd31f981e12fcedf41adb56.json

427 ms

e88ea265b014eaf3673798a08148cc5f.json

e88ea265b014eaf3673798a08148cc5f.json

373 ms

66e1c6183d4f78a503c4d2f06ee94782.json

66e1c6183d4f78a503c4d2f06ee94782.json

960 ms

43c39e779b6e0f9faa37b0da71f4d993.json

43c39e779b6e0f9faa37b0da71f4d993.json

983 ms

0a292c697a4b5270fe3fc40ab79bbc1c.json

0a292c697a4b5270fe3fc40ab79bbc1c.json

981 ms

b4c989b6b55cc370b7d407082472dc0e.json

b4c989b6b55cc370b7d407082472dc0e.json

958 ms

b46510b2f41f2709bc3c2dc939dcc210.json

b46510b2f41f2709bc3c2dc939dcc210.json

957 ms

0ba9ef623cd31f981e12fcedf41adb56.json

0ba9ef623cd31f981e12fcedf41adb56.json

956 ms

e88ea265b014eaf3673798a08148cc5f.json

e88ea265b014eaf3673798a08148cc5f.json

1347 ms

66e1c6183d4f78a503c4d2f06ee94782.json

66e1c6183d4f78a503c4d2f06ee94782.json

1339 ms

klaviyo_analytics.js

klaviyo_analytics.js

1207 ms

modules

modules

841 ms

collect

collect

191 ms

ga-audiences

ga-audiences

31 ms

gist-embed-00e78e58c090554178aab653e8643d5e.css

gist-embed-00e78e58c090554178aab653e8643d5e.css

237 ms

onsite

onsite

414 ms

0.7cfa86ad6aae84df1f18.css

0.7cfa86ad6aae84df1f18.css

422 ms

styles.1757ddef7c8731c410e2.js

styles.1757ddef7c8731c410e2.js

871 ms

sentry.5ae9269795f89fbb9935.js

sentry.5ae9269795f89fbb9935.js

895 ms

vendors~signupForms.d73b1e68bbd199f3ffc8.js

vendors~signupForms.d73b1e68bbd199f3ffc8.js

922 ms

signupForms.0381c4cc194cf6a244b2.js

signupForms.0381c4cc194cf6a244b2.js

891 ms

Accessibility Review

dylanjh.com accessibility score

68

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

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

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

dylanjh.com best practices score

75

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

Browser errors were logged to the console

SEO Factors

dylanjh.com SEO score

91

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

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

    N/A

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Dylanjh.com 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 Dylanjh.com main page’s claimed encoding is . 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

dylanjh.com

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