Tools & Wizards About Us
jnjestore.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

jnjestore.com

MyStore - For J&J Employees & Retirees

Page Load Speed

2.7 sec in total

First Response

193 ms

Resources Loaded

2.4 sec

Page Rendered

104 ms

jnjestore.com screenshot

About Website

Click here to check amazing Jnje Store content. Otherwise, check out these important facts you probably never knew about jnjestore.com

Shop MyStore today and get great savings and value on products from Johnson & Johnson - just for J&J Employees and Retirees.

Visit jnjestore.com

Key Findings

We analyzed Jnjestore.com page load time and found that the first response time was 193 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

jnjestore.com performance score

0

Network Requests Diagram

jnjestore.com

193 ms

sitelogin.do

606 ms

jquery-1.4.min.js

34 ms

jquery.hoverIntent.minified.js

71 ms

jquery.bgiframe.min.js

102 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 Jnjestore.com, 63% (33 requests) were made to Jjmystore.com and 23% (12 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (606 ms) relates to the external source Jjmystore.com.

Page Optimization Overview & Recommendations

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

Content Size

948.8 kB

After Optimization

356.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Jnjestore.com main page is 948.8 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. 40% of websites need less resources to load. Javascripts take 785.9 kB which makes up the majority of the site volume.

HTML Optimization

-74%

Potential reduce by 10.0 kB

  • Original 13.4 kB
  • After minification 11.9 kB
  • After compression 3.5 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. This page needs HTML code to be minified as it can gain 1.5 kB, which is 11% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 10.0 kB or 74% of the original size.

Image Optimization

-3%

Potential reduce by 845 B

  • Original 27.8 kB
  • After minification 26.9 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. Jnje Store images are well optimized though.

JavaScript Optimization

-61%

Potential reduce by 477.0 kB

  • Original 785.9 kB
  • After minification 625.8 kB
  • After compression 308.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 477.0 kB or 61% of the original size.

CSS Optimization

-86%

Potential reduce by 104.7 kB

  • Original 121.7 kB
  • After minification 89.8 kB
  • After compression 17.0 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. Jnjestore.com needs all CSS files to be minified and compressed as it can save up to 104.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (70%)

Requests Now

50

After Optimization

15

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

jnjestore.com

jnjestore.com

193 ms

sitelogin.do

sitelogin.do

606 ms

jquery-1.4.min.js

jquery-1.4.min.js

34 ms

jquery.hoverIntent.minified.js

jquery.hoverIntent.minified.js

71 ms

jquery.bgiframe.min.js

jquery.bgiframe.min.js

102 ms

jquery.popDown.js

jquery.popDown.js

117 ms

jquery.autocomplete.js

jquery.autocomplete.js

125 ms

jquery.validate-1.7.min.js

jquery.validate-1.7.min.js

131 ms

clientSideValidation.js

clientSideValidation.js

128 ms

clientsidevalidation.css

clientsidevalidation.css

136 ms

pqv.compressed.js

pqv.compressed.js

156 ms

default.css

default.css

143 ms

pqv.css

pqv.css

153 ms

simpleTooltip.js

simpleTooltip.js

174 ms

satelliteLib-a77040281e8ad94d1a2e4c30d4df757c9e6fed98.js

satelliteLib-a77040281e8ad94d1a2e4c30d4df757c9e6fed98.js

71 ms

jjmystore.css

jjmystore.css

182 ms

headerScripts.js

headerScripts.js

182 ms

cookieCheck.js

cookieCheck.js

183 ms

AccordionCheckout.js

AccordionCheckout.js

187 ms

oo_style.css

oo_style.css

186 ms

oo_engine.min.js

oo_engine.min.js

186 ms

oo_conf_float.js

oo_conf_float.js

191 ms

footerScripts.js

footerScripts.js

190 ms

ga.js

ga.js

36 ms

satellite-53299f495e4bd66166000812.js

satellite-53299f495e4bd66166000812.js

17 ms

satellite-54cf99c96437370016c00000.js

satellite-54cf99c96437370016c00000.js

28 ms

satellite-56bce3f264746d25ab001de3.js

satellite-56bce3f264746d25ab001de3.js

35 ms

satellite-5364125bc80de2df990000a5.js

satellite-5364125bc80de2df990000a5.js

56 ms

satellite-5367cf849975ed0b470001fa.js

satellite-5367cf849975ed0b470001fa.js

66 ms

satellite-5399ba205822a8384e000212.js

satellite-5399ba205822a8384e000212.js

54 ms

satellite-5399ba205822a8384e000213.js

satellite-5399ba205822a8384e000213.js

67 ms

satellite-546cb5106562330015480800.js

satellite-546cb5106562330015480800.js

63 ms

satellite-5668819864746d7dbf003309.js

satellite-5668819864746d7dbf003309.js

66 ms

satellite-56706d0964746d571e007329.js

satellite-56706d0964746d571e007329.js

67 ms

tms.js

tms.js

84 ms

__utm.gif

__utm.gif

42 ms

account_bg_landing.jpg

account_bg_landing.jpg

33 ms

logo01.gif

logo01.gif

27 ms

welcomemystore_mhd.gif

welcomemystore_mhd.gif

36 ms

employee_mhd.gif

employee_mhd.gif

33 ms

spacer01.gif

spacer01.gif

31 ms

pleaseclickhere_btn_off.gif

pleaseclickhere_btn_off.gif

34 ms

retiree_mhd.gif

retiree_mhd.gif

60 ms

navbottom_bg.gif

navbottom_bg.gif

74 ms

footerruler.gif

footerruler.gif

74 ms

copyrightImage.gif

copyrightImage.gif

75 ms

s-code-contents-8a9515957a836dfc5e047f730ab7fdd6e3bfc312.js

s-code-contents-8a9515957a836dfc5e047f730ab7fdd6e3bfc312.js

33 ms

_Incapsula_Resource

_Incapsula_Resource

378 ms

oo_float_icon.gif

oo_float_icon.gif

57 ms

id

id

32 ms

id

id

39 ms

s56458474695682

s56458474695682

12 ms

SEO Factors

jnjestore.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

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

jnjestore.com

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