Tools & Wizards About Us
8mobile.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

8mobile.com

8 Mobile

Page Load Speed

2.4 sec in total

First Response

182 ms

Resources Loaded

2.1 sec

Page Rendered

137 ms

8mobile.com screenshot

About Website

Visit 8mobile.com now to see the best up-to-date 8 Mobile content for United States and also check out these interesting facts you probably never knew about 8mobile.com

Sell your old and unused mobile phones to us! Come to 8 mobile to recycle your old and used mobile phones for cash. Trade in your old and used mobile phone online now and we'll send money to your acco...

Visit 8mobile.com

Key Findings

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

8mobile.com performance score

0

Network Requests Diagram

8mobile.com

182 ms

www.8mobile.com

623 ms

style.css

500 ms

flybox.css

249 ms

jquery.fancybox-1.3.4.css

332 ms

Our browser made a total of 70 requests to load all elements on the main page. We found that 91% of them (64 requests) were addressed to the original 8mobile.com, 3% (2 requests) were made to Google-analytics.com and 3% (2 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (623 ms) belongs to the original domain 8mobile.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 235.8 kB (44%)

Content Size

536.3 kB

After Optimization

300.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 8mobile.com main page is 536.3 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. 20% of websites need less resources to load. Images take 229.7 kB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 22.1 kB

  • Original 26.4 kB
  • After minification 24.4 kB
  • After compression 4.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. 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 22.1 kB or 84% of the original size.

Image Optimization

-2%

Potential reduce by 4.5 kB

  • Original 229.7 kB
  • After minification 225.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. 8 Mobile images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 150.6 kB

  • Original 207.8 kB
  • After minification 169.4 kB
  • After compression 57.2 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 150.6 kB or 72% of the original size.

CSS Optimization

-81%

Potential reduce by 58.6 kB

  • Original 72.4 kB
  • After minification 57.2 kB
  • After compression 13.8 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. 8mobile.com needs all CSS files to be minified and compressed as it can save up to 58.6 kB or 81% of the original size.

Requests Breakdown

Number of requests can be reduced by 27 (40%)

Requests Now

67

After Optimization

40

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 67 CSS, Javascripts, AJAX and image requests in order to completely render the main page of 8 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 7 to 1 for JavaScripts and as a result speed up the page load time.

Network Requests Diagram

8mobile.com

8mobile.com

182 ms

www.8mobile.com

www.8mobile.com

623 ms

style.css

style.css

500 ms

flybox.css

flybox.css

249 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

332 ms

autogen.phones.js

autogen.phones.js

597 ms

g.jquery.js

g.jquery.js

438 ms

flybox.js

flybox.js

250 ms

jquery.fancybox-1.3.4.pack.js

jquery.fancybox-1.3.4.pack.js

496 ms

client.js

client.js

421 ms

tracking.js

tracking.js

10 ms

popup_page_fade.png

popup_page_fade.png

86 ms

logo_bg.png

logo_bg.png

85 ms

8-mobile.png

8-mobile.png

87 ms

slogan.png

slogan.png

171 ms

topmenu_left.png

topmenu_left.png

89 ms

topmenu_right.png

topmenu_right.png

90 ms

topmenu_bg.png

topmenu_bg.png

171 ms

topmenu_del.png

topmenu_del.png

178 ms

input_left.png

input_left.png

172 ms

input_bg.png

input_bg.png

180 ms

input_right.png

input_right.png

180 ms

search_go_btn.png

search_go_btn.png

252 ms

make-apple.png

make-apple.png

253 ms

make-blackberry.png

make-blackberry.png

254 ms

make-htc.png

make-htc.png

256 ms

make-lg.png

make-lg.png

258 ms

make-motorola.png

make-motorola.png

260 ms

make-nokia.png

make-nokia.png

334 ms

make-o2.png

make-o2.png

334 ms

make-samsung.png

make-samsung.png

335 ms

make-sony-ericsson.png

make-sony-ericsson.png

340 ms

phone-slider_left2.png

phone-slider_left2.png

342 ms

phone-slider_right2.png

phone-slider_right2.png

342 ms

fade-left.png

fade-left.png

416 ms

fade-right.png

fade-right.png

417 ms

8-mobile-hd-iphone-6-64gb.jpg

8-mobile-hd-iphone-6-64gb.jpg

417 ms

8-mobile-hd-iphone-6s-64gb.jpg

8-mobile-hd-iphone-6s-64gb.jpg

424 ms

8-mobile-hd-iphone-6s-plus-128gb.jpg

8-mobile-hd-iphone-6s-plus-128gb.jpg

426 ms

8-mobile-hd-samsung-note-4-N910.jpg

8-mobile-hd-samsung-note-4-N910.jpg

427 ms

8-mobile-hd-samsung-galaxy-s6-edge-g925.jpg

8-mobile-hd-samsung-galaxy-s6-edge-g925.jpg

498 ms

8-mobile-hd-iphone-7-256gb.jpg

8-mobile-hd-iphone-7-256gb.jpg

501 ms

8-mobile-hd-htc-10.jpg

8-mobile-hd-htc-10.jpg

502 ms

find_promo2.png

find_promo2.png

509 ms

facebook70.png

facebook70.png

510 ms

findbox_bg.png

findbox_bg.png

511 ms

ga.js

ga.js

15 ms

findbox_input_left.png

findbox_input_left.png

535 ms

like.php

like.php

89 ms

__utm.gif

__utm.gif

15 ms

findbox_input_bg.png

findbox_input_bg.png

508 ms

findbox_input_right.png

findbox_input_right.png

507 ms

btn_dropdown.png

btn_dropdown.png

515 ms

redbtn_bg.png

redbtn_bg.png

514 ms

select-phone-image.png

select-phone-image.png

515 ms

4qFiRLLPSF7.js

4qFiRLLPSF7.js

28 ms

lH1ibRl5GKq.png

lH1ibRl5GKq.png

30 ms

socialbox-bottom.png

socialbox-bottom.png

502 ms

socialbox-top.png

socialbox-top.png

504 ms

socialbox-bg.png

socialbox-bg.png

499 ms

icon30_facebook.png

icon30_facebook.png

508 ms

icon30_twitter.png

icon30_twitter.png

508 ms

icon30_8mobile.png

icon30_8mobile.png

508 ms

foooter_ls_logo.png

foooter_ls_logo.png

502 ms

footer_bg.png

footer_bg.png

504 ms

footer_bg_splash.png

footer_bg_splash.png

504 ms

footer_checkmend.png

footer_checkmend.png

514 ms

footer_comodo_ssl.png

footer_comodo_ssl.png

513 ms

foooter_rs.png

foooter_rs.png

513 ms

weee.png

weee.png

502 ms

SEO Factors

8mobile.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 8mobile.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 8mobile.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

8mobile.com

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