Tools & Wizards About Us
seewhy.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

seewhy.com

CRM and Customer Experience (CX) Systems for Your Enterprise | SAP

Page Load Speed

3.6 sec in total

First Response

177 ms

Resources Loaded

3.1 sec

Page Rendered

317 ms

seewhy.com screenshot

About Website

Click here to check amazing Seewhy content for United States. Otherwise, check out these important facts you probably never knew about seewhy.com

Win new customers for life with CRM and customer experience (CX) solutions based on SAP C/4HANA, formerly SAP Hybris, Gigya, and CoreSystems solutions. Learn more.

Visit seewhy.com

Key Findings

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

Performance Metrics

seewhy.com performance score

0

Network Requests Diagram

seewhy.com

177 ms

marketing-conversion

504 ms

marketing-convert

238 ms

combined.css

285 ms

omni.epx

193 ms

Our browser made a total of 62 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Seewhy.com, 68% (42 requests) were made to Hybris.com and 8% (5 requests) were made to Assets.adobedtm.com. The less responsive or slowest element that took the longest time to load (926 ms) relates to the external source Global.sap.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 238.2 kB (50%)

Content Size

471.9 kB

After Optimization

233.8 kB

  • HTML
  • Images
  • JavaScript

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

HTML Optimization

-75%

Potential reduce by 27.0 kB

  • Original 35.9 kB
  • After minification 33.5 kB
  • After compression 8.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 27.0 kB or 75% of the original size.

Image Optimization

-0%

Potential reduce by 12 B

  • Original 119.2 kB
  • After minification 119.2 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. Seewhy images are well optimized though.

JavaScript Optimization

-67%

Potential reduce by 211.1 kB

  • Original 316.8 kB
  • After minification 284.3 kB
  • After compression 105.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 211.1 kB or 67% of the original size.

Requests Breakdown

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

Requests Now

56

After Optimization

31

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

seewhy.com

seewhy.com

177 ms

marketing-conversion

marketing-conversion

504 ms

marketing-convert

marketing-convert

238 ms

combined.css

combined.css

285 ms

omni.epx

omni.epx

193 ms

satelliteLib-fb5feb5655c08e1b85f43fcc9819e14212a3fe43.js

satelliteLib-fb5feb5655c08e1b85f43fcc9819e14212a3fe43.js

62 ms

combined.js

combined.js

577 ms

omni.epx

omni.epx

926 ms

satellite-55771feb6630390014c70300.js

satellite-55771feb6630390014c70300.js

32 ms

satellite-55771feb6630390014c80300.js

satellite-55771feb6630390014c80300.js

46 ms

analytics.js

analytics.js

70 ms

privacy.js

privacy.js

505 ms

8810170155038.png

8810170155038.png

112 ms

get-in-touch.png

get-in-touch.png

108 ms

search.png

search.png

107 ms

0159.svg

0159.svg

278 ms

0160.svg

0160.svg

274 ms

048.svg

048.svg

272 ms

download-box-2015-cheapcaribbean-big.jpg

download-box-2015-cheapcaribbean-big.jpg

462 ms

download-box-2015-cheapcaribbean-small.jpg

download-box-2015-cheapcaribbean-small.jpg

463 ms

download-box-2015-case-study-patricia-pepe-big.jpg

download-box-2015-case-study-patricia-pepe-big.jpg

467 ms

download-box-2015-case-study-patricia-pepe-small.jpg

download-box-2015-case-study-patricia-pepe-small.jpg

464 ms

download-box-2015-mobile-commerce-report-big.jpg

download-box-2015-mobile-commerce-report-big.jpg

470 ms

download-box-2015-mobile-commerce-report-small.jpg

download-box-2015-mobile-commerce-report-small.jpg

374 ms

DINWebPro.woff

DINWebPro.woff

554 ms

DINWebPro-Bold.woff

DINWebPro-Bold.woff

640 ms

bg-gradient-modal-cart.png

bg-gradient-modal-cart.png

540 ms

icon-bulb.svg

icon-bulb.svg

538 ms

icon-gift.png

icon-gift.png

541 ms

roiCalc-carts.png

roiCalc-carts.png

553 ms

roiCalc-orders.png

roiCalc-orders.png

639 ms

spofdlb-download-icon.svg

spofdlb-download-icon.svg

622 ms

spofdlb-play-icon.svg

spofdlb-play-icon.svg

630 ms

spofsn-close-icon.png

spofsn-close-icon.png

631 ms

spofbq-icon-before.png

spofbq-icon-before.png

632 ms

spofbq-icon-after.png

spofbq-icon-after.png

707 ms

foc-icon.png

foc-icon.png

717 ms

footer-icon-presented2.svg

footer-icon-presented2.svg

713 ms

news_icon.png

news_icon.png

719 ms

footer-icon-twitter.svg

footer-icon-twitter.svg

720 ms

footer-icon-facebook.svg

footer-icon-facebook.svg

722 ms

footer-icon-linkedin.svg

footer-icon-linkedin.svg

804 ms

footer-icon-googleplus.svg

footer-icon-googleplus.svg

807 ms

footer-icon-youtube.svg

footer-icon-youtube.svg

811 ms

footer-icon-xing.svg

footer-icon-xing.svg

816 ms

footer-icon-weibo.svg

footer-icon-weibo.svg

817 ms

footer-bottom-arrow.png

footer-bottom-arrow.png

820 ms

satellite-55895d8d376233001400068b.js

satellite-55895d8d376233001400068b.js

44 ms

satellite-557721dd3735660017e30200.js

satellite-557721dd3735660017e30200.js

34 ms

collect

collect

18 ms

collect

collect

13 ms

s47192691585514

s47192691585514

167 ms

dx_upx_0DPKjoICb7.js

dx_upx_0DPKjoICb7.js

227 ms

overlay.png

overlay.png

693 ms

references_icon_close_hover.png

references_icon_close_hover.png

699 ms

language-dropdown.png

language-dropdown.png

701 ms

1x1_Gif.gif

1x1_Gif.gif

72 ms

cookie-pixel-fire-sap.html

cookie-pixel-fire-sap.html

30 ms

cookie-pixel-lib.js

cookie-pixel-lib.js

30 ms

sapustservlet

sapustservlet

97 ms

piwik.js

piwik.js

213 ms

piwik_plugin.js

piwik_plugin.js

112 ms

SEO Factors

seewhy.com SEO score

0

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

seewhy.com

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