Tools & Wizards About Us
hotmobile.co.il screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

hotmobile.co.il

Request Rejected

Page Load Speed

8.3 sec in total

First Response

767 ms

Resources Loaded

7.2 sec

Page Rendered

407 ms

hotmobile.co.il screenshot

About Website

Click here to check amazing Hotmobile content for Israel. Otherwise, check out these important facts you probably never knew about hotmobile.co.il

הוט מובייל מציעה חבילות שיחה, גלישה ו-SMS במחיר קבוע וללא הגבלה. ניתן לרכוש גם חבילות לעסקים ומכשירים סלולריים כולל אייפון או סמארטפון

Visit hotmobile.co.il

Key Findings

We analyzed Hotmobile.co.il page load time and found that the first response time was 767 ms and then it took 7.6 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

hotmobile.co.il performance score

0

Network Requests Diagram

www.hotmobile.co.il

767 ms

default.aspx

1138 ms

controls.css

311 ms

Menu.css

432 ms

corev4.css

894 ms

Our browser made a total of 92 requests to load all elements on the main page. We found that 85% of them (78 requests) were addressed to the original Hotmobile.co.il, 7% (6 requests) were made to Hotnet.net.il and 2% (2 requests) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (2.5 sec) belongs to the original domain Hotmobile.co.il.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.5 MB (37%)

Content Size

4.2 MB

After Optimization

2.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hotmobile.co.il main page is 4.2 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. 40% of websites need less resources to load. Images take 2.4 MB which makes up the majority of the site volume.

HTML Optimization

-70%

Potential reduce by 67.6 kB

  • Original 97.2 kB
  • After minification 86.2 kB
  • After compression 29.6 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 11.0 kB, which is 11% 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 67.6 kB or 70% of the original size.

Image Optimization

-2%

Potential reduce by 38.1 kB

  • Original 2.4 MB
  • After minification 2.3 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. Hotmobile images are well optimized though.

JavaScript Optimization

-75%

Potential reduce by 663.5 kB

  • Original 881.2 kB
  • After minification 720.9 kB
  • After compression 217.8 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 663.5 kB or 75% of the original size.

CSS Optimization

-89%

Potential reduce by 775.0 kB

  • Original 866.9 kB
  • After minification 779.9 kB
  • After compression 91.9 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. Hotmobile.co.il needs all CSS files to be minified and compressed as it can save up to 775.0 kB or 89% of the original size.

Requests Breakdown

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

Requests Now

88

After Optimization

61

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

www.hotmobile.co.il

www.hotmobile.co.il

767 ms

default.aspx

default.aspx

1138 ms

controls.css

controls.css

311 ms

Menu.css

Menu.css

432 ms

corev4.css

corev4.css

894 ms

common.css

common.css

451 ms

common.css

common.css

647 ms

common.css

common.css

1110 ms

jquery-ui.css

jquery-ui.css

477 ms

anythingslider.css

anythingslider.css

588 ms

WebResource.axd

WebResource.axd

465 ms

blank.js

blank.js

486 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

883 ms

Plugins.js

Plugins.js

1784 ms

common.js

common.js

954 ms

common.js

common.js

666 ms

MainNavigation.js

MainNavigation.js

830 ms

common.js

common.js

913 ms

hm_logo.png

hm_logo.png

991 ms

58387_mobile_4G_application_1366x337.jpg

58387_mobile_4G_application_1366x337.jpg

1732 ms

55041_mobile_roaming_plazma_1366x337.jpg

55041_mobile_roaming_plazma_1366x337.jpg

1780 ms

57816_mobile_web_plazmot.jpg

57816_mobile_web_plazmot.jpg

1707 ms

59129_mobile_plazma_site_1366x337_v1-11-02-16.jpg

59129_mobile_plazma_site_1366x337_v1-11-02-16.jpg

1724 ms

56246_mobile_iphone6s_sale_plazma_1366x337a.jpg

56246_mobile_iphone6s_sale_plazma_1366x337a.jpg

1591 ms

support_section01.png

support_section01.png

1752 ms

support_section02.png

support_section02.png

1866 ms

support_section03.png

support_section03.png

1884 ms

support_section04.png

support_section04.png

1881 ms

blank.gif

blank.gif

1909 ms

abroad_sample01.png

abroad_sample01.png

1944 ms

abroad_sample02.png

abroad_sample02.png

1945 ms

bullets_banner_sample01.png

bullets_banner_sample01.png

2025 ms

bullets_banner_sample02.png

bullets_banner_sample02.png

2033 ms

bullets_banner_sample03.png

bullets_banner_sample03.png

2045 ms

H6900262_site_banner_1366-174.jpg

H6900262_site_banner_1366-174.jpg

2527 ms

H6900262_site_banner_640x320.jpg

H6900262_site_banner_640x320.jpg

2408 ms

conversion.js

conversion.js

62 ms

footer_hot_logo.png

footer_hot_logo.png

2100 ms

footer_hotnet_logo.png

footer_hotnet_logo.png

2182 ms

footer_hot017_logo.png

footer_hot017_logo.png

2025 ms

init.js

init.js

1295 ms

ScriptResource.axd

ScriptResource.axd

1273 ms

dc.js

dc.js

82 ms

fbevents.js

fbevents.js

303 ms

bgximg.png

bgximg.png

170 ms

upper_header_rtl.png

upper_header_rtl.png

159 ms

header_register_corner_rtl.png

header_register_corner_rtl.png

167 ms

header_register_toggle_arr_rtl.png

header_register_toggle_arr_rtl.png

170 ms

header_login_submit_rtl.png

header_login_submit_rtl.png

173 ms

header_youtube.png

header_youtube.png

305 ms

header_google.png

header_google.png

310 ms

header_facebook.png

header_facebook.png

328 ms

header_twitter.png

header_twitter.png

334 ms

header_accessibility.png

header_accessibility.png

328 ms

header_devider.png

header_devider.png

332 ms

__utm.gif

__utm.gif

14 ms

banner.htm

banner.htm

742 ms

float_menu_bullet.png

float_menu_bullet.png

431 ms

ga-audiences

ga-audiences

104 ms

home_deals_plus.png

home_deals_plus.png

418 ms

header_login_submit_rtl.png

header_login_submit_rtl.png

445 ms

support_bg2.jpg

support_bg2.jpg

439 ms

support_services_arr_rtl.png

support_services_arr_rtl.png

446 ms

self_service_icon09.png

self_service_icon09.png

450 ms

self_service_icon01.png

self_service_icon01.png

568 ms

self_service_icon02.png

self_service_icon02.png

581 ms

self_service_icon03_rtl.png

self_service_icon03_rtl.png

592 ms

self_service_icon04_rtl.png

self_service_icon04_rtl.png

603 ms

self_service_icon07.png

self_service_icon07.png

597 ms

self_service_icon06.png

self_service_icon06.png

604 ms

self_service_icon08.png

self_service_icon08.png

717 ms

self_service_icon05_rtl.png

self_service_icon05_rtl.png

736 ms

sim_icon.png

sim_icon.png

743 ms

hm_question.png

hm_question.png

751 ms

support_bg.jpg

support_bg.jpg

910 ms

footer_twitter.png

footer_twitter.png

760 ms

footer_facebook.png

footer_facebook.png

868 ms

footer_google.png

footer_google.png

892 ms

footer_youtube.png

footer_youtube.png

894 ms

footer_accessibility.png

footer_accessibility.png

906 ms

73 ms

Ach.ashx

Ach.ashx

849 ms

ui-bg_highlight-soft_100_eeeeee_1x100.png

ui-bg_highlight-soft_100_eeeeee_1x100.png

964 ms

15 ms

ui-icons_222222_256x240.png

ui-icons_222222_256x240.png

944 ms

header_lang_arr.png

header_lang_arr.png

950 ms

110 ms

banner.css

banner.css

173 ms

jquery-1.7.1.min.js

jquery-1.7.1.min.js

781 ms

jquery.responsive_countdown.js

jquery.responsive_countdown.js

1024 ms

banner_image.jpg

banner_image.jpg

1449 ms

banner_image_mobile.jpg

banner_image_mobile.jpg

1175 ms

SEO Factors

hotmobile.co.il SEO score

0

Language and Encoding

  • Language Detected

    IW

  • Language Claimed

    HE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotmobile.co.il can be misinterpreted by Google and other search engines. Our service has detected that Hebrew is used on the page, and it does not match the claimed language. Our system also found out that Hotmobile.co.il 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

hotmobile.co.il

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