Tools & Wizards About Us
bludotink.com screenshot

Report Summary

  • 60

    Performance

    Renders faster than
    76% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 62% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 93

    SEO

    Google-friendlier than
    84% of websites

bludotink.com

T-shirt Printing | Layton, UT | Blu Dot Ink

Page Load Speed

4.2 sec in total

First Response

121 ms

Resources Loaded

2.5 sec

Page Rendered

1.6 sec

bludotink.com screenshot

About Website

Click here to check amazing Blu Dot Ink content. Otherwise, check out these important facts you probably never knew about bludotink.com

Layton, Utah. Blu Dot Ink has been offering custom screen printing and embroidery for over 15 years. Call us at 801-544-9468.

Visit bludotink.com

Key Findings

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

Performance Metrics

bludotink.com performance score

60

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.1 s

82/100

10%

LCP (Largest Contentful Paint)

Value3.2 s

73/100

25%

SI (Speed Index)

Value3.6 s

87/100

10%

TBT (Total Blocking Time)

Value880 ms

32/100

30%

CLS (Cumulative Layout Shift)

Value0.152

75/100

15%

TTI (Time to Interactive)

Value8.4 s

39/100

10%

Network Requests Diagram

www.bludotink.com

121 ms

775d778.jpg

451 ms

jquery.min.js

387 ms

d-js-runtime-one-package.min.js

437 ms

d-js-one-runtime-layouts-package.min.js

385 ms

Our browser made a total of 71 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Bludotink.com, 42% (30 requests) were made to Cdn.website.thryv.com and 24% (17 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (905 ms) relates to the external source Irp-cdn.multiscreensite.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 635.5 kB (42%)

Content Size

1.5 MB

After Optimization

893.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Bludotink.com main page is 1.5 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. Images take 729.5 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 91.2 kB

  • Original 118.1 kB
  • After minification 113.6 kB
  • After compression 26.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 91.2 kB or 77% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 729.5 kB
  • After minification 729.5 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. Blu Dot Ink images are well optimized though.

JavaScript Optimization

-27%

Potential reduce by 20.8 kB

  • Original 76.1 kB
  • After minification 76.1 kB
  • After compression 55.4 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 20.8 kB or 27% of the original size.

CSS Optimization

-87%

Potential reduce by 523.5 kB

  • Original 605.0 kB
  • After minification 603.9 kB
  • After compression 81.4 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. Bludotink.com needs all CSS files to be minified and compressed as it can save up to 523.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 10 (22%)

Requests Now

46

After Optimization

36

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.bludotink.com

www.bludotink.com

121 ms

775d778.jpg

775d778.jpg

451 ms

jquery.min.js

jquery.min.js

387 ms

d-js-runtime-one-package.min.js

d-js-runtime-one-package.min.js

437 ms

d-js-one-runtime-layouts-package.min.js

d-js-one-runtime-layouts-package.min.js

385 ms

d-js-one-runtime-layouts-desktop.min.js

d-js-one-runtime-layouts-desktop.min.js

434 ms

dxmscript.min.js

dxmscript.min.js

480 ms

768.jpg

768.jpg

61 ms

865.png

865.png

60 ms

074.jpg

074.jpg

60 ms

076.jpg

076.jpg

45 ms

075d778.jpg

075d778.jpg

52 ms

901.jpg

901.jpg

53 ms

233.png

233.png

50 ms

894.png

894.png

66 ms

479.jpg

479.jpg

52 ms

480.jpg

480.jpg

64 ms

481.jpg

481.jpg

65 ms

482.jpg

482.jpg

65 ms

483.png

483.png

146 ms

484.png

484.png

147 ms

485.png

485.png

146 ms

486.jpg

486.jpg

146 ms

487.jpg

487.jpg

347 ms

488.png

488.png

352 ms

489.jpg

489.jpg

353 ms

490.png

490.png

352 ms

491.jpg

491.jpg

361 ms

492.png

492.png

362 ms

493.jpg

493.jpg

436 ms

494.png

494.png

463 ms

495.png

495.png

437 ms

bgg.png

bgg.png

457 ms

ga.js

ga.js

129 ms

sp-2.0.0-dm-0.1.min.js

sp-2.0.0-dm-0.1.min.js

560 ms

css

css

882 ms

css-font-package-v2.min.css

css-font-package-v2.min.css

87 ms

d-css-runtime-desktop-one-package-new.min.css

d-css-runtime-desktop-one-package-new.min.css

25 ms

4b28541d819dfc4d03b7fa233cbf2f34.css

4b28541d819dfc4d03b7fa233cbf2f34.css

635 ms

38203d1f5ebf4661a34dfabb0d9b9580_1.min.css

38203d1f5ebf4661a34dfabb0d9b9580_1.min.css

905 ms

38203d1f5ebf4661a34dfabb0d9b9580_home_1.min.css

38203d1f5ebf4661a34dfabb0d9b9580_home_1.min.css

862 ms

__utm.gif

__utm.gif

392 ms

__utm.gif

__utm.gif

187 ms

__utm.gif

__utm.gif

385 ms

__utm.gif

__utm.gif

388 ms

dm-social-icons.ttf

dm-social-icons.ttf

76 ms

dm-common-icons.ttf

dm-common-icons.ttf

76 ms

collect

collect

592 ms

collect

collect

394 ms

235d778.jpg

235d778.jpg

191 ms

ga-audiences

ga-audiences

140 ms

ga-audiences

ga-audiences

142 ms

215d778.jpg

215d778.jpg

203 ms

518d778.jpg

518d778.jpg

125 ms

KFOmCnqEu92Fr1Mu7GxM.woff

KFOmCnqEu92Fr1Mu7GxM.woff

34 ms

KFOlCnqEu92Fr1MmEU9fChc-.woff

KFOlCnqEu92Fr1MmEU9fChc-.woff

35 ms

KFOlCnqEu92Fr1MmSU5fChc-.woff

KFOlCnqEu92Fr1MmSU5fChc-.woff

100 ms

KFOkCnqEu92Fr1MmgVxGIzQ.woff

KFOkCnqEu92Fr1MmgVxGIzQ.woff

103 ms

KFOlCnqEu92Fr1MmWUlfChc-.woff

KFOlCnqEu92Fr1MmWUlfChc-.woff

155 ms

KFOlCnqEu92Fr1MmYUtfChc-.woff

KFOlCnqEu92Fr1MmYUtfChc-.woff

102 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58i-xA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkP8o58i-xA.woff

168 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58i-xA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkM0o58i-xA.woff

168 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58i-xA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkKEo58i-xA.woff

166 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv58i-xA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkCEv58i-xA.woff

155 ms

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58i-xA.woff

6xK-dSZaM9iE8KbpRA_LJ3z8mH9BOJvgkBgv58i-xA.woff

166 ms

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7j.woff

6xK3dSBYKcSV-LCoeQqfX1RYOo3qNq7j.woff

170 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ik4zwmRdo.woff

169 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i94_wmRdo.woff

169 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3i54rwmRdo.woff

171 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3ig4vwmRdo.woff

170 ms

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdo.woff

6xKydSBYKcSV-LCoeQqfX1RYOo3iu4nwmRdo.woff

170 ms

Accessibility Review

bludotink.com accessibility score

86

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

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

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

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

bludotink.com SEO score

93

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

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

bludotink.com

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