Tools & Wizards About Us
alomobile.ro screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

alomobile.ro

Telefoane mobile ieftine | alomobile.ro - alomobile telefoane ieftine | alomobile.ro | Preturi telefoane noi

Page Load Speed

5.4 sec in total

First Response

490 ms

Resources Loaded

4.6 sec

Page Rendered

305 ms

alomobile.ro screenshot

About Website

Click here to check amazing Alo Mobile content. Otherwise, check out these important facts you probably never knew about alomobile.ro

Telefoane | Telefoane Mobile | GSM | Preturi telefoane | Nokia | Samsung | Apple | LG | HTC | Telefoane de vanzare

Visit alomobile.ro

Key Findings

We analyzed Alomobile.ro page load time and found that the first response time was 490 ms and then it took 5 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.

Performance Metrics

alomobile.ro performance score

0

Network Requests Diagram

alomobile.ro

490 ms

home.asp

853 ms

pcHeaderFooter.css

263 ms

pcStorefront.css

393 ms

newsletter_subscribe.css

263 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 72% of them (79 requests) were addressed to the original Alomobile.ro, 4% (4 requests) were made to Google-analytics.com and 4% (4 requests) were made to W.sharethis.com. The less responsive or slowest element that took the longest time to load (1.4 sec) belongs to the original domain Alomobile.ro.

Page Optimization Overview & Recommendations

Page size can be reduced by 887.5 kB (34%)

Content Size

2.6 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Alomobile.ro main page is 2.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. 50% of websites need less resources to load. Images take 1.6 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 58.3 kB

  • Original 70.4 kB
  • After minification 54.8 kB
  • After compression 12.1 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 15.6 kB, which is 22% 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 58.3 kB or 83% of the original size.

Image Optimization

-10%

Potential reduce by 151.4 kB

  • Original 1.6 MB
  • After minification 1.4 MB

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. Alo Mobile images are well optimized though.

JavaScript Optimization

-72%

Potential reduce by 584.5 kB

  • Original 807.0 kB
  • After minification 776.2 kB
  • After compression 222.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 584.5 kB or 72% of the original size.

CSS Optimization

-85%

Potential reduce by 93.2 kB

  • Original 109.4 kB
  • After minification 80.6 kB
  • After compression 16.1 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. Alomobile.ro needs all CSS files to be minified and compressed as it can save up to 93.2 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 51 (50%)

Requests Now

103

After Optimization

52

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

alomobile.ro

alomobile.ro

490 ms

home.asp

home.asp

853 ms

pcHeaderFooter.css

pcHeaderFooter.css

263 ms

pcStorefront.css

pcStorefront.css

393 ms

newsletter_subscribe.css

newsletter_subscribe.css

263 ms

colorbox.css

colorbox.css

263 ms

jquery-ui-1.7.2.custom.css

jquery-ui-1.7.2.custom.css

398 ms

onepagecheckout.css

onepagecheckout.css

261 ms

jquery-1.3.2.min.js

jquery-1.3.2.min.js

529 ms

jquery-ui-1.7.2.custom.min.js

jquery-ui-1.7.2.custom.min.js

799 ms

jquery.validate.min.OPC.js

jquery.validate.min.OPC.js

525 ms

jquery.bgiframe.pack.js

jquery.bgiframe.pack.js

394 ms

jquery.form.js

jquery.form.js

524 ms

newsletter_subscribe_form.js

newsletter_subscribe_form.js

526 ms

jquery.cycle.lite.min.js

jquery.cycle.lite.min.js

534 ms

jquery.colorbox-min.js

jquery.colorbox-min.js

658 ms

buttons.js

buttons.js

10 ms

scs.css

scs.css

657 ms

scs.js

scs.js

661 ms

screen.css

screen.css

654 ms

highslide.html.packed.js

highslide.html.packed.js

835 ms

ei-tooltip.css

ei-tooltip.css

670 ms

ei-tooltip.js

ei-tooltip.js

672 ms

XHConn.js

XHConn.js

671 ms

shopmania-store-ro.gif

shopmania-store-ro.gif

333 ms

bg-container.jpg

bg-container.jpg

1301 ms

logo.jpg

logo.jpg

160 ms

buton_cauta.gif

buton_cauta.gif

159 ms

banner-1.jpg

banner-1.jpg

984 ms

home-1.jpg

home-1.jpg

157 ms

home-2.jpg

home-2.jpg

332 ms

home-3.jpg

home-3.jpg

332 ms

home-4.jpg

home-4.jpg

332 ms

home-5.jpg

home-5.jpg

333 ms

home-6.jpg

home-6.jpg

393 ms

home-7.jpg

home-7.jpg

395 ms

home-8.jpg

home-8.jpg

398 ms

sony_s.gif

sony_s.gif

400 ms

sony-xperia-z3-01_2059_thumb.jpg

sony-xperia-z3-01_2059_thumb.jpg

526 ms

pc_button_comanda_rapida.gif

pc_button_comanda_rapida.gif

527 ms

lg_lg_153_normal.gif

lg_lg_153_normal.gif

535 ms

lg-g3-5_540_thumb.jpg

lg-g3-5_540_thumb.jpg

536 ms

lg_samsu_1624_normal.gif

lg_samsu_1624_normal.gif

974 ms

samsung-galaxy-s5-mini-1_491_thumb.jpg

samsung-galaxy-s5-mini-1_491_thumb.jpg

975 ms

samsung-galaxy-s6-3_975_thumb.jpg

samsung-galaxy-s6-3_975_thumb.jpg

975 ms

lg_htc_964_normal.gif

lg_htc_964_normal.gif

975 ms

htc-one-m9-1_1961_thumb.jpg

htc-one-m9-1_1961_thumb.jpg

977 ms

s6edge_2338_thumb.jpg

s6edge_2338_thumb.jpg

977 ms

4947c463566cec7d693b5dd62e1e84c6.image.380x277_551_normal.jpg

4947c463566cec7d693b5dd62e1e84c6.image.380x277_551_normal.jpg

978 ms

iphone-6srose_1971_thumb.jpg

iphone-6srose_1971_thumb.jpg

977 ms

iphone-6sgold_2212_thumb.jpg

iphone-6sgold_2212_thumb.jpg

980 ms

alcatel_logo_normal.png

alcatel_logo_normal.png

981 ms

alcatel-2005_1979_thumb.jpg

alcatel-2005_1979_thumb.jpg

981 ms

alcatel-2007_1111_thumb.jpg

alcatel-2007_1111_thumb.jpg

980 ms

sus_off.gif

sus_off.gif

1039 ms

icon-fb.jpg

icon-fb.jpg

1064 ms

icon-ig.jpg

icon-ig.jpg

1066 ms

compari.png

compari.png

1067 ms

logoprice.gif

logoprice.gif

1067 ms

zoomin.cur

zoomin.cur

1151 ms

bgd_top_nav.jpg

bgd_top_nav.jpg

1174 ms

logo.js

logo.js

524 ms

ga.js

ga.js

10 ms

analytics.js

analytics.js

80 ms

getAllAppDefault.esi

getAllAppDefault.esi

182 ms

__utm.gif

__utm.gif

24 ms

separator_top_horiz_nav.jpg

separator_top_horiz_nav.jpg

1045 ms

btn_collapse.gif

btn_collapse.gif

1047 ms

collect

collect

17 ms

btn_expand.gif

btn_expand.gif

1032 ms

widget_v2.135.js

widget_v2.135.js

15 ms

__$$__stringtable_lang_nl.js

__$$__stringtable_lang_nl.js

9 ms

up-left-combo.png

up-left-combo.png

976 ms

lower-left-combo.png

lower-left-combo.png

1001 ms

up-right-combo.png

up-right-combo.png

1433 ms

lower-right-combo.png

lower-right-combo.png

1003 ms

getSegment.php

getSegment.php

24 ms

checkOAuth.esi

checkOAuth.esi

76 ms

t.dhj

t.dhj

57 ms

topcap.png

topcap.png

945 ms

titlemiddle.png

titlemiddle.png

1033 ms

contentmiddle.png

contentmiddle.png

1041 ms

bottomcap.png

bottomcap.png

1062 ms

t.dhj

t.dhj

47 ms

cm

cm

25 ms

x35248

x35248

110 ms

s-3271.xgi

s-3271.xgi

7 ms

15 ms

hbpix

hbpix

114 ms

14 ms

pixel

pixel

21 ms

xrefid.xgi

xrefid.xgi

7 ms

bgd_modul_produsH.png

bgd_modul_produsH.png

949 ms

pixel

pixel

15 ms

2981

2981

21 ms

logo_1.png

logo_1.png

411 ms

avatar_simple_visitor.png

avatar_simple_visitor.png

89 ms

aL63HcygAAVYuCCsAAA==

aL63HcygAAVYuCCsAAA==

2 ms

index.2d85e55d89f85ae69e4f2ca5ab9438b7.html

index.2d85e55d89f85ae69e4f2ca5ab9438b7.html

10 ms

buttons.ab966a004186897711de4a5ed256c924.css

buttons.ab966a004186897711de4a5ed256c924.css

107 ms

stcommon.2b05accc08f1ee42fe1983647ab923ea.js

stcommon.2b05accc08f1ee42fe1983647ab923ea.js

15 ms

st.1188278743c14064d5e8ae56c8ada29c.js

st.1188278743c14064d5e8ae56c8ada29c.js

27 ms

cauti_on.jpg

cauti_on.jpg

135 ms

looker_on.jpg

looker_on.jpg

137 ms

federal_on.jpg

federal_on.jpg

139 ms

smartnetbook_on.jpg

smartnetbook_on.jpg

137 ms

livrare_on.jpg

livrare_on.jpg

139 ms

rounded-white.png

rounded-white.png

305 ms

zoomout.cur

zoomout.cur

264 ms

loader.white.gif

loader.white.gif

266 ms

SEO Factors

alomobile.ro SEO score

0

Language and Encoding

  • Language Detected

    RO

  • Language Claimed

    N/A

  • Encoding

    UTF-8

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

alomobile.ro

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