Tools & Wizards About Us
my.samsungmobile.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

my.samsungmobile.com

Galaxy Smartphones | Samsung Malaysia

Page Load Speed

6.9 sec in total

First Response

287 ms

Resources Loaded

4.9 sec

Page Rendered

1.8 sec

my.samsungmobile.com screenshot

About Website

Welcome to my.samsungmobile.com homepage info - get ready to check My Samsung Mobile best content for India right away, or after learning these important things about my.samsungmobile.com

SAMSUNG Samsung Malaysia Galaxy Smartphone

Visit my.samsungmobile.com

Key Findings

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

Performance Metrics

my.samsungmobile.com performance score

0

Network Requests Diagram

287 ms

425 ms

samsung.min.js

60 ms

ss-location.js

40 ms

Bootstrap.js

44 ms

Our browser made a total of 138 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original My.samsungmobile.com, 13% (18 requests) were made to Images.samsung.com and 4% (5 requests) were made to Google.com. The less responsive or slowest element that took the longest time to load (1.1 sec) relates to the external source Go.affec.tv.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.0 MB (66%)

Content Size

4.5 MB

After Optimization

1.6 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of My.samsungmobile.com main page is 4.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. 85% 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. Javascripts take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-91%

Potential reduce by 226.7 kB

  • Original 250.1 kB
  • After minification 180.3 kB
  • After compression 23.4 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 69.8 kB, which is 28% 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 226.7 kB or 91% of the original size.

Image Optimization

-14%

Potential reduce by 152.9 kB

  • Original 1.1 MB
  • After minification 970.3 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. Obviously, My Samsung Mobile needs image optimization as it can save up to 152.9 kB or 14% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-80%

Potential reduce by 2.0 MB

  • Original 2.4 MB
  • After minification 1.7 MB
  • After compression 476.1 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 2.0 MB or 80% of the original size.

CSS Optimization

-88%

Potential reduce by 624.9 kB

  • Original 708.2 kB
  • After minification 676.9 kB
  • After compression 83.3 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. My.samsungmobile.com needs all CSS files to be minified and compressed as it can save up to 624.9 kB or 88% of the original size.

Requests Breakdown

Number of requests can be reduced by 76 (59%)

Requests Now

128

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

287 ms

425 ms

samsung.min.js

samsung.min.js

60 ms

ss-location.js

ss-location.js

40 ms

Bootstrap.js

Bootstrap.js

44 ms

samsung.css

samsung.css

43 ms

samsung.css

samsung.css

43 ms

navigation.css

navigation.css

43 ms

navigation.css

navigation.css

44 ms

nav.css

nav.css

305 ms

utilityIcons.css

utilityIcons.css

303 ms

utilityIcons.css

utilityIcons.css

304 ms

compare-button.js

compare-button.js

304 ms

cookie.js

cookie.js

302 ms

wishlist-button.js

wishlist-button.js

329 ms

search_ac-global.js

search_ac-global.js

329 ms

estoreif-queue.js

estoreif-queue.js

325 ms

estoreif.js

estoreif.js

366 ms

personalization.js

personalization.js

338 ms

offerRFY.js

offerRFY.js

400 ms

deepLinkManager.js

deepLinkManager.js

375 ms

category-ver2.css

category-ver2.css

374 ms

category-ver2.css

category-ver2.css

461 ms

samsungIcoLabel.css

samsungIcoLabel.css

375 ms

common-func.js

common-func.js

382 ms

family_option.js

family_option.js

359 ms

new-category.js

new-category.js

361 ms

category-printer-accessory.js

category-printer-accessory.js

367 ms

video-player.js

video-player.js

366 ms

bootstrap-popover.js

bootstrap-popover.js

374 ms

online_retailer.js

online_retailer.js

367 ms

BrightcoveExperiences.js

BrightcoveExperiences.js

305 ms

SmartPlayerAPI.js

SmartPlayerAPI.js

307 ms

auth.js

auth.js

370 ms

web_std.css

web_std.css

366 ms

s_code_next.js

s_code_next.js

378 ms

smg.new.common.min.js

smg.new.common.min.js

374 ms

smg.messages.js

smg.messages.js

368 ms

samsung-icon.css

samsung-icon.css

176 ms

samsung.cloud-iq.com

samsung.cloud-iq.com

316 ms

serverComponent.php

serverComponent.php

147 ms

ebOneTag.js

ebOneTag.js

145 ms

livechat.js

livechat.js

144 ms

hero.css

hero.css

38 ms

filter-sortby.css

filter-sortby.css

46 ms

product-card.css

product-card.css

41 ms

module-small.css

module-small.css

48 ms

compare.css

compare.css

56 ms

find-my-device.css

find-my-device.css

52 ms

recommend-items.css

recommend-items.css

50 ms

bg-navigation.gif

bg-navigation.gif

91 ms

logo.svg

logo.svg

91 ms

ico-windows.svg

ico-windows.svg

92 ms

ico-search.svg

ico-search.svg

115 ms

loading-animation.gif

loading-animation.gif

62 ms

award1.png

award1.png

58 ms

award2.png

award2.png

59 ms

award3.png

award3.png

81 ms

award4.png

award4.png

78 ms

award5.png

award5.png

61 ms

award6.png

award6.png

60 ms

question.png

question.png

81 ms

bb86058af4e31aa2c944808aa8d31660.js

bb86058af4e31aa2c944808aa8d31660.js

65 ms

hero-arrow.png

hero-arrow.png

184 ms

d96d1c36b93eb9ae33a8b894cbdd0d31.js

d96d1c36b93eb9ae33a8b894cbdd0d31.js

174 ms

SamsungIF_Rg.woff

SamsungIF_Rg.woff

173 ms

my_SM-A510FZDFXME_000000001_Front_gold_thumb

my_SM-A510FZDFXME_000000001_Front_gold_thumb

109 ms

my_SM-A710FZDFXME_000000001_Front_gold_thumb

my_SM-A710FZDFXME_000000001_Front_gold_thumb

217 ms

my_SM-A310FZDDXME_000000001_Front_gold_thumb

my_SM-A310FZDDXME_000000001_Front_gold_thumb

219 ms

my_SM-N9208ZWUXME_002_FrontPen_pink_thumb

my_SM-N9208ZWUXME_002_FrontPen_pink_thumb

219 ms

my_SM-G935FZDUXME_000000001_Front_gold_thumb

my_SM-G935FZDUXME_000000001_Front_gold_thumb

217 ms

my_SM-G9287ZKAXME_001_Front_gold_thumb

my_SM-G9287ZKAXME_001_Front_gold_thumb

219 ms

my_SM-G920FZKAXME_006_Front_black_thumb

my_SM-G920FZKAXME_006_Front_black_thumb

218 ms

my_SM-G925FZDAXME_001_Front_gold_thumb

my_SM-G925FZDAXME_001_Front_gold_thumb

218 ms

my_SM-N915FZKEXME_000264074_Front-Pen_black_thumb

my_SM-N915FZKEXME_000264074_Front-Pen_black_thumb

219 ms

my_SM-N910CZIEXTE_001_front_white_thumb

my_SM-N910CZIEXTE_001_front_white_thumb

218 ms

my_SM-A800FZDEXME_000000001_Front_gold_thumb

my_SM-A800FZDEXME_000000001_Front_gold_thumb

216 ms

my_SM-A700FZWDXME_000273976_Front_SS_white_thumb

my_SM-A700FZWDXME_000273976_Front_SS_white_thumb

215 ms

my_SM-A500FZSAXME_001_front_black_thumb

my_SM-A500FZSAXME_001_front_black_thumb

216 ms

my_SM-J200GZDDXME_000000001_Front_gold_thumb

my_SM-J200GZDDXME_000000001_Front_gold_thumb

232 ms

my_SM-J110GZKDXME_000000001_Front_black_thumb

my_SM-J110GZKDXME_000000001_Front_black_thumb

230 ms

my_SM-J500GZWDXME_001_gold_gold_thumb

my_SM-J500GZWDXME_001_gold_gold_thumb

230 ms

my_SM-J700FZWDXME_012_Front_gold_thumb

my_SM-J700FZWDXME_012_Front_gold_thumb

233 ms

my_SM-G318HZKZMYM_001_Front_white_thumb

my_SM-G318HZKZMYM_001_Front_white_thumb

232 ms

samsungIcon.woff

samsungIcon.woff

217 ms

Desktop_Category_final-2-2.jpg

Desktop_Category_final-2-2.jpg

545 ms

01_Noble_KV_Pink_1920x1026-1-0.jpg

01_Noble_KV_Pink_1920x1026-1-0.jpg

545 ms

01_Zero2_KV_1920x1026-2-0.jpg

01_Zero2_KV_1920x1026-2-0.jpg

543 ms

conversion_async.js

conversion_async.js

28 ms

SamsungIF_Bd.woff

SamsungIF_Bd.woff

489 ms

561fd1361b6f11000f780324

561fd1361b6f11000f780324

319 ms

fbevents.js

fbevents.js

155 ms

tag.js

tag.js

99 ms

152 ms

194 ms

capture-apps-4.9.1.js

capture-apps-4.9.1.js

96 ms

140 ms

51e52394c2590846cd8e877b

51e52394c2590846cd8e877b

1131 ms

nav-ir.png

nav-ir.png

54 ms

ico_Malaysia.gif

ico_Malaysia.gif

97 ms

analytics.js

analytics.js

103 ms

gtm.js

gtm.js

873 ms

iframeStorage.html

iframeStorage.html

963 ms

1DA9F572-6F92-4683-A93E-AA04B0F33668

1DA9F572-6F92-4683-A93E-AA04B0F33668

666 ms

s49281753902323

s49281753902323

30 ms

Serving

Serving

943 ms

bounce

bounce

808 ms

iframe_api

iframe_api

873 ms

ss-kv-pause.png

ss-kv-pause.png

742 ms

recommendModel

recommendModel

940 ms

selectRFYOfferCategoryList

selectRFYOfferCategoryList

612 ms

bounce

bounce

180 ms

sync

sync

180 ms

ss-dot.png

ss-dot.png

173 ms

ss-dot-current.png

ss-dot-current.png

172 ms

collect

collect

106 ms

appsmanagerinit

appsmanagerinit

370 ms

sync

sync

115 ms

collect

collect

79 ms

collect

collect

216 ms

iframeStorage.js

iframeStorage.js

71 ms

pixel.png

pixel.png

87 ms

activityi;src=4077367;type=invmedia;cat=0qigemmn;ord=2315622949972.7485

activityi;src=4077367;type=invmedia;cat=0qigemmn;ord=2315622949972.7485

166 ms

oct.js

oct.js

126 ms

fbds.js

fbds.js

63 ms

www-widgetapi.js

www-widgetapi.js

118 ms

71 ms

91 ms

20 ms

ga-audiences

ga-audiences

23 ms

pixel.png

pixel.png

10 ms

ga-audiences

ga-audiences

23 ms

adsct

adsct

138 ms

adsct

adsct

60 ms

offer

offer

330 ms

pixel

pixel

47 ms

s7roadshow-250x250-0.jpg

s7roadshow-250x250-0.jpg

53 ms

note5_marchPWP250x250-3-1.jpg

note5_marchPWP250x250-3-1.jpg

137 ms

SEO Factors

my.samsungmobile.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 My.samsungmobile.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 My.samsungmobile.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

my.samsungmobile.com

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