Tools & Wizards About Us
initialencounter.com screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 92

    Accessibility

    Visual factors better than
    that of 78% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 100

    SEO

    Google-friendlier than
    94% of websites

initialencounter.com

Home | Initial Encounter Embroidery | Pequannock NJ

Page Load Speed

2.6 sec in total

First Response

289 ms

Resources Loaded

2.2 sec

Page Rendered

59 ms

initialencounter.com screenshot

About Website

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

Initial Encounter offers Custom Embroidery, Monogramming, Custom T-shirts, Sports Apparel/Accessories, Wedding Gifts, Corporate Apparel, Baby Items

Visit initialencounter.com

Key Findings

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

initialencounter.com performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.4 s

36/100

10%

LCP (Largest Contentful Paint)

Value5.2 s

23/100

25%

SI (Speed Index)

Value5.9 s

48/100

10%

TBT (Total Blocking Time)

Value1,640 ms

12/100

30%

CLS (Cumulative Layout Shift)

Value0.024

100/100

15%

TTI (Time to Interactive)

Value18.3 s

3/100

10%

Network Requests Diagram

www.initialencounter.com

289 ms

minified.js

25 ms

focus-within-polyfill.js

53 ms

polyfill.min.js

22 ms

bae80a_b6e5125acc3e4c9b8cd9854928b04340~mv2.jpg

381 ms

Our browser made a total of 52 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Initialencounter.com, 40% (21 requests) were made to Static.wixstatic.com and 29% (15 requests) were made to Static.parastorage.com. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Static.wixstatic.com.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

559.5 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Initialencounter.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. 35% of websites need less resources to load. HTML takes 803.9 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 631.8 kB

  • Original 803.9 kB
  • After minification 802.1 kB
  • After compression 172.1 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 631.8 kB or 79% of the original size.

Image Optimization

-5%

Potential reduce by 6.6 kB

  • Original 137.3 kB
  • After minification 130.8 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. Initial Encounter images are well optimized though.

JavaScript Optimization

-52%

Potential reduce by 277.3 kB

  • Original 533.9 kB
  • After minification 533.9 kB
  • After compression 256.6 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 277.3 kB or 52% of the original size.

Requests Breakdown

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

Requests Now

36

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.initialencounter.com

www.initialencounter.com

289 ms

minified.js

minified.js

25 ms

focus-within-polyfill.js

focus-within-polyfill.js

53 ms

polyfill.min.js

polyfill.min.js

22 ms

bae80a_b6e5125acc3e4c9b8cd9854928b04340~mv2.jpg

bae80a_b6e5125acc3e4c9b8cd9854928b04340~mv2.jpg

381 ms

o.jpg

o.jpg

396 ms

7e209e_1bb32f1bb3884639931dbe49ede20b36~mv2.jpg

7e209e_1bb32f1bb3884639931dbe49ede20b36~mv2.jpg

326 ms

7e209e_0c5fd22078d4450faf06bf5571c6fc50~mv2.jpg

7e209e_0c5fd22078d4450faf06bf5571c6fc50~mv2.jpg

293 ms

7e209e_87668dd714d745eaa92e6f115898d6e7~mv2_d_2617_1795_s_2.jpg

7e209e_87668dd714d745eaa92e6f115898d6e7~mv2_d_2617_1795_s_2.jpg

295 ms

38567b0b5eb55f8eba96f60fa6356630.png

38567b0b5eb55f8eba96f60fa6356630.png

46 ms

IMG_3669.jpg

IMG_3669.jpg

451 ms

IMG_3682.jpg

IMG_3682.jpg

682 ms

IMG_3685.jpg

IMG_3685.jpg

802 ms

IMG_3675.jpg

IMG_3675.jpg

645 ms

IMG_3681.jpg

IMG_3681.jpg

734 ms

7e209e_1d191a32c8dd41cda1b1982567c5d968~mv2_d_4032_3024_s_4_2.jpg

7e209e_1d191a32c8dd41cda1b1982567c5d968~mv2_d_4032_3024_s_4_2.jpg

670 ms

7e209e_674100d6b64f48c8b6d3a4314a323e1c~mv2_d_3024_3024_s_4_2.jpg

7e209e_674100d6b64f48c8b6d3a4314a323e1c~mv2_d_3024_3024_s_4_2.jpg

754 ms

7e209e_e3da534901b44262b3ced190be159118~mv2.jpg

7e209e_e3da534901b44262b3ced190be159118~mv2.jpg

956 ms

7e209e_030ea8dbe5a2460587a4e919bc65f801~mv2.png

7e209e_030ea8dbe5a2460587a4e919bc65f801~mv2.png

980 ms

7e209e_488de89f3a044b5783d28eef5d793d56~mv2_d_4032_3024_s_4_2.jpg

7e209e_488de89f3a044b5783d28eef5d793d56~mv2_d_4032_3024_s_4_2.jpg

927 ms

7e209e_83541c179f334eed9a94834a3b5ebed9~mv2.jpg

7e209e_83541c179f334eed9a94834a3b5ebed9~mv2.jpg

998 ms

7e209e_dd59cd186e454e8a823d0076802cc63e~mv2_d_3667_3015_s_4_2.jpg

7e209e_dd59cd186e454e8a823d0076802cc63e~mv2_d_3667_3015_s_4_2.jpg

1064 ms

7e209e_91fdce3af2324e4aa0acbf440256f2ed~mv2_d_2548_2623_s_4_2.jpg

7e209e_91fdce3af2324e4aa0acbf440256f2ed~mv2_d_2548_2623_s_4_2.jpg

1071 ms

7e209e_c96ed81ffa1e4b538d979d33b4ec5413~mv2_d_3034_2999_s_4_2.jpg

7e209e_c96ed81ffa1e4b538d979d33b4ec5413~mv2_d_3034_2999_s_4_2.jpg

1300 ms

7e209e_0a22ad3d6abf4447b978f1550d02e743~mv2_d_4032_3024_s_4_2.jpg

7e209e_0a22ad3d6abf4447b978f1550d02e743~mv2_d_4032_3024_s_4_2.jpg

1288 ms

bundle.min.js

bundle.min.js

72 ms

thunderbolt-commons.b70ee867.bundle.min.js

thunderbolt-commons.b70ee867.bundle.min.js

34 ms

main.317ed945.bundle.min.js

main.317ed945.bundle.min.js

34 ms

main.renderer.1d21f023.bundle.min.js

main.renderer.1d21f023.bundle.min.js

38 ms

lodash.min.js

lodash.min.js

41 ms

react.production.min.js

react.production.min.js

51 ms

react-dom.production.min.js

react-dom.production.min.js

52 ms

siteTags.bundle.min.js

siteTags.bundle.min.js

29 ms

92 ms

91 ms

90 ms

100 ms

94 ms

92 ms

126 ms

125 ms

125 ms

131 ms

129 ms

132 ms

deprecation-en.v5.html

deprecation-en.v5.html

8 ms

bolt-performance

bolt-performance

11 ms

deprecation-style.v5.css

deprecation-style.v5.css

5 ms

right-arrow.svg

right-arrow.svg

12 ms

WixMadeforDisplay_W_Bd.woff

WixMadeforDisplay_W_Bd.woff

5 ms

WixMadeforText_W_Bd.woff

WixMadeforText_W_Bd.woff

5 ms

WixMadeforText_W_Rg.woff

WixMadeforText_W_Rg.woff

8 ms

Accessibility Review

initialencounter.com accessibility score

92

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

Buttons do not have an accessible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

initialencounter.com SEO score

100

Search Engine Optimization Advices

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

initialencounter.com

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