Tools & Wizards About Us
sphone.de screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

sphone.de

Smartphones mit Vertrag zu Top-Preisen auf sPhone.de

Page Load Speed

7.6 sec in total

First Response

355 ms

Resources Loaded

6.7 sec

Page Rendered

540 ms

sphone.de screenshot

About Website

Click here to check amazing SPhone content for Germany. Otherwise, check out these important facts you probably never knew about sphone.de

Alles rund ums Thema Smartphone und Tablet finden Sie auf sPhone.de: Top-Angebote für Smartphones mit Vertrag, News und Smartphone Testberichte u.v.m.

Visit sphone.de

Key Findings

We analyzed Sphone.de page load time and found that the first response time was 355 ms and then it took 7.2 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster.

Performance Metrics

sphone.de performance score

0

Network Requests Diagram

sphone.de

355 ms

www.sphone.de

1243 ms

cms_basics.css.php

819 ms

mobiledevice.css.php

504 ms

article.css

279 ms

Our browser made a total of 139 requests to load all elements on the main page. We found that 11% of them (15 requests) were addressed to the original Sphone.de, 18% (25 requests) were made to Bilder.sphone.de and 11% (15 requests) were made to Imagesrv.adition.com. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source Bilder.sphone.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 854.7 kB (54%)

Content Size

1.6 MB

After Optimization

721.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Sphone.de main page is 1.6 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. 55% of websites need less resources to load. Javascripts take 824.2 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 96.9 kB

  • Original 126.9 kB
  • After minification 120.6 kB
  • After compression 30.0 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 96.9 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 30.6 kB

  • Original 377.2 kB
  • After minification 346.6 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. SPhone images are well optimized though.

JavaScript Optimization

-63%

Potential reduce by 521.8 kB

  • Original 824.2 kB
  • After minification 817.8 kB
  • After compression 302.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 521.8 kB or 63% of the original size.

CSS Optimization

-83%

Potential reduce by 205.5 kB

  • Original 247.7 kB
  • After minification 246.3 kB
  • After compression 42.2 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. Sphone.de needs all CSS files to be minified and compressed as it can save up to 205.5 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 84 (64%)

Requests Now

132

After Optimization

48

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

sphone.de

sphone.de

355 ms

www.sphone.de

www.sphone.de

1243 ms

cms_basics.css.php

cms_basics.css.php

819 ms

mobiledevice.css.php

mobiledevice.css.php

504 ms

article.css

article.css

279 ms

cms_basics.js.php

cms_basics.js.php

969 ms

adition.js

adition.js

260 ms

iam.js

iam.js

409 ms

my_ad_integration.js

my_ad_integration.js

281 ms

my_ad_integration.css

my_ad_integration.css

539 ms

849 ms

692 ms

css

css

24 ms

css

css

34 ms

js

js

280 ms

js

js

280 ms

js

js

281 ms

js

js

281 ms

analytics.js

analytics.js

24 ms

samsung-galaxy-s6_0101w120_7563.png

samsung-galaxy-s6_0101w120_7563.png

461 ms

android_0101w16_976.png

android_0101w16_976.png

725 ms

apple-iphone-6_0101w120_6999.png

apple-iphone-6_0101w120_6999.png

827 ms

apple_0101w16_699.png

apple_0101w16_699.png

725 ms

huawei-mate-s_0101w120_8871.png

huawei-mate-s_0101w120_8871.png

900 ms

apple-iphone-6s_0101w120_8984.png

apple-iphone-6s_0101w120_8984.png

900 ms

samsung-galaxy-s7_0101w120_9847.png

samsung-galaxy-s7_0101w120_9847.png

900 ms

samsung-galaxy-s6-edge_0101w120_7559.png

samsung-galaxy-s6-edge_0101w120_7559.png

1099 ms

apple-iphone-6s-plus_0101w120_8985.png

apple-iphone-6s-plus_0101w120_8985.png

1100 ms

sony-xperia-z5_0101w120_8853.png

sony-xperia-z5_0101w120_8853.png

1204 ms

youtube_0000w100_1058.png

youtube_0000w100_1058.png

1201 ms

nokia-lumia-1520_0403w350_5699.jpg

nokia-lumia-1520_0403w350_5699.jpg

1420 ms

samsung-galaxy-s7-edge_0403w350_9854.jpg

samsung-galaxy-s7-edge_0403w350_9854.jpg

1341 ms

apple-iphone-6_0403w350_7066.jpg

apple-iphone-6_0403w350_7066.jpg

1672 ms

apple_logo_699.png

apple_logo_699.png

1489 ms

google_logo_8818.png

google_logo_8818.png

1489 ms

htc_logo_713.png

htc_logo_713.png

1489 ms

huawei_logo_714.png

huawei_logo_714.png

1694 ms

lg_logo_716.png

lg_logo_716.png

1836 ms

microsoft_logo_9162.png

microsoft_logo_9162.png

1726 ms

motorola_logo_734.png

motorola_logo_734.png

1727 ms

samsung_logo_740.png

samsung_logo_740.png

1738 ms

handy_0201w280_441.jpg

handy_0201w280_441.jpg

2161 ms

tablet-mit-smartphone-de_0201w280_4281.jpg

tablet-mit-smartphone-de_0201w280_4281.jpg

2167 ms

umts_0201w280_3220.jpg

umts_0201w280_3220.jpg

2216 ms

uid.html

uid.html

93 ms

tx.io

tx.io

192 ms

collect

collect

21 ms

tx.io

tx.io

99 ms

verivoxde.js

verivoxde.js

454 ms

globalV6.js

globalV6.js

70 ms

gpt.js

gpt.js

25 ms

rc

rc

228 ms

c.ount

c.ount

266 ms

gw.js

gw.js

182 ms

pql

pql

35 ms

adplayer.min.css

adplayer.min.css

28 ms

adplayer.min.js

adplayer.min.js

63 ms

pubads_impl_82.js

pubads_impl_82.js

9 ms

container.html

container.html

8 ms

pixel

pixel

16 ms

pixel

pixel

19 ms

default.js

default.js

168 ms

e6859dabf5ada4775bdb986a33bf9

e6859dabf5ada4775bdb986a33bf9

40 ms

oba_icon.png

oba_icon.png

27 ms

260244,260240,260242

260244,260240,260242

133 ms

p.min.js

p.min.js

8 ms

data

data

346 ms

194222462.js

194222462.js

118 ms

c.ount

c.ount

170 ms

ads

ads

56 ms

rs.js

rs.js

35 ms

osd.js

osd.js

20 ms

rpc.flow

rpc.flow

122 ms

vce_st.js

vce_st.js

12 ms

ads

ads

42 ms

c.ount

c.ount

181 ms

p2

p2

15 ms

p

p

7 ms

p

p

52 ms

rpc.flow

rpc.flow

66 ms

sphone-logo.svg

sphone-logo.svg

401 ms

ads

ads

38 ms

c.ount

c.ount

110 ms

i12font.woff

i12font.woff

691 ms

p

p

32 ms

rpc.flow

rpc.flow

32 ms

header-punkte.png

header-punkte.png

301 ms

arrow-block.gif

arrow-block.gif

300 ms

arrow.png

arrow.png

300 ms

banner

banner

199 ms

videoseries

videoseries

136 ms

banner

banner

532 ms

adex.js

adex.js

328 ms

adrtxtag.min.js

adrtxtag.min.js

249 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

36 ms

www-embed-player.js

www-embed-player.js

62 ms

image_0000l300_8479.jpg

image_0000l300_8479.jpg

496 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

57 ms

ad_status.js

ad_status.js

55 ms

banner

banner

176 ms

2.gif

2.gif

90 ms

activeview

activeview

51 ms

t.js

t.js

90 ms

activeview

activeview

14 ms

image_0201l300_9292.jpg

image_0201l300_9292.jpg

461 ms

banner

banner

172 ms

1.gif

1.gif

86 ms

analytic.js

analytic.js

205 ms

204 ms

300x250.html

300x250.html

453 ms

ftg_t_v_bk.min.js

ftg_t_v_bk.min.js

540 ms

impression.php

impression.php

581 ms

postview.gif

postview.gif

562 ms

banner

banner

184 ms

pixel

pixel

35 ms

cm.gif

cm.gif

96 ms

img

img

29 ms

brandlift.php

brandlift.php

135 ms

p

p

12 ms

2.gif

2.gif

90 ms

AditionH5_ClickTags.js

AditionH5_ClickTags.js

114 ms

edge.6.0.0.min.js

edge.6.0.0.min.js

529 ms

300x250_edge.js

300x250_edge.js

104 ms

400 ms

xbf.html

xbf.html

415 ms

300x250_edge.js

300x250_edge.js

91 ms

tp1.png

tp1.png

100 ms

tp2.png

tp2.png

99 ms

device2.png

device2.png

160 ms

device1.png

device1.png

188 ms

logo.png

logo.png

246 ms

flipCoin_front.png

flipCoin_front.png

263 ms

flipCoin_back.png

flipCoin_back.png

262 ms

cursor.png

cursor.png

267 ms

287 ms

ftg_frame.min.js

ftg_frame.min.js

378 ms

2.gif

2.gif

365 ms

adex.js

adex.js

485 ms

2.gif

2.gif

218 ms

SEO Factors

sphone.de SEO score

0

Language and Encoding

  • Language Detected

    DE

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Sphone.de can be misinterpreted by Google and other search engines. Our service has detected that German 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 Sphone.de 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

sphone.de

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