Tools & Wizards About Us
largerbox.co screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

largerbox.co

Largerbox company | کمپانی لارجر باکس | شرکة لارجرباکس

Page Load Speed

981 ms in total

First Response

125 ms

Resources Loaded

581 ms

Page Rendered

275 ms

largerbox.co screenshot

About Website

Click here to check amazing Largerbox content. Otherwise, check out these important facts you probably never knew about largerbox.co

Largerbox enlargement devices. Larger Box dispositivos de la ampliación. لارجر باکس أجهزة التوسيع . لارجرباکس دستگاه بزرگ کننده

Visit largerbox.co

Key Findings

We analyzed Largerbox.co page load time and found that the first response time was 125 ms and then it took 856 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 20% of websites can load faster.

Performance Metrics

largerbox.co performance score

0

Network Requests Diagram

largerbox.co

125 ms

total-compressed.css

51 ms

style.css

64 ms

shop_functions.js

67 ms

global_functions.js

66 ms

Our browser made a total of 69 requests to load all elements on the main page. We found that 88% of them (61 requests) were addressed to the original Largerbox.co, 4% (3 requests) were made to Google-analytics.com and 3% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (214 ms) belongs to the original domain Largerbox.co.

Page Optimization Overview & Recommendations

Page size can be reduced by 294.6 kB (41%)

Content Size

716.0 kB

After Optimization

421.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Largerbox.co main page is 716.0 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. 45% of websites need less resources to load. Images take 348.1 kB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 72.8 kB

  • Original 85.6 kB
  • After minification 52.9 kB
  • After compression 12.9 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 32.8 kB, which is 38% 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 72.8 kB or 85% of the original size.

Image Optimization

-4%

Potential reduce by 14.0 kB

  • Original 348.1 kB
  • After minification 334.0 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. Largerbox images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 116.3 kB

  • Original 175.0 kB
  • After minification 161.2 kB
  • After compression 58.7 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 116.3 kB or 66% of the original size.

CSS Optimization

-85%

Potential reduce by 91.5 kB

  • Original 107.4 kB
  • After minification 80.9 kB
  • After compression 15.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. Largerbox.co needs all CSS files to be minified and compressed as it can save up to 91.5 kB or 85% of the original size.

Requests Breakdown

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

Requests Now

64

After Optimization

37

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

largerbox.co

largerbox.co

125 ms

total-compressed.css

total-compressed.css

51 ms

style.css

style.css

64 ms

shop_functions.js

shop_functions.js

67 ms

global_functions.js

global_functions.js

66 ms

mootools.js

mootools.js

101 ms

script.js

script.js

71 ms

plusone.js

plusone.js

70 ms

flowplayer.min.js

flowplayer.min.js

74 ms

bumpbox.js

bumpbox.js

76 ms

accordion.css

accordion.css

75 ms

byslidemenu-1.1.js

byslidemenu-1.1.js

76 ms

global.js

global.js

97 ms

cb=gapi.loaded_0

cb=gapi.loaded_0

37 ms

ga.js

ga.js

32 ms

js

js

15 ms

seal_1321311.js

seal_1321311.js

75 ms

main_background.gif

main_background.gif

75 ms

menu_background.gif

menu_background.gif

75 ms

home.png

home.png

76 ms

menu_level_background_2.png

menu_level_background_2.png

77 ms

menu_andropen_gold_6.png

menu_andropen_gold_6.png

80 ms

menu_andropeyronie.png

menu_andropeyronie.png

79 ms

menu_androvacuum.png

menu_androvacuum.png

77 ms

menu_ere.png

menu_ere.png

80 ms

menu_androhair.png

menu_androhair.png

102 ms

menu_andropharmiapen.png

menu_andropharmiapen.png

81 ms

contact_letter_icon.jpg

contact_letter_icon.jpg

85 ms

family_01.jpg

family_01.jpg

84 ms

button_green_bg.gif

button_green_bg.gif

82 ms

largerbox.jpg

largerbox.jpg

87 ms

vacium.jpg

vacium.jpg

102 ms

pointer_yellow.gif

pointer_yellow.gif

100 ms

peyronie_right.jpg

peyronie_right.jpg

100 ms

bodegon_androvacuum.jpg

bodegon_androvacuum.jpg

101 ms

bodegon_andropharmia.jpg

bodegon_andropharmia.jpg

106 ms

enlargement_left.jpg

enlargement_left.jpg

121 ms

bodegon_andro.jpg

bodegon_andro.jpg

128 ms

hellstrom_ground.jpg

hellstrom_ground.jpg

121 ms

hellstrom_ground_overlap.png

hellstrom_ground_overlap.png

145 ms

faix_ground.jpg

faix_ground.jpg

131 ms

faix_ground_overlap.png

faix_ground_overlap.png

178 ms

studies_row.jpg

studies_row.jpg

167 ms

peyronie_disease_home.jpg

peyronie_disease_home.jpg

144 ms

se_health_monitor_home.jpg

se_health_monitor_home.jpg

160 ms

media_list.gif

media_list.gif

164 ms

tab_accordion.gif

tab_accordion.gif

176 ms

ico_accordion_closed_big.gif

ico_accordion_closed_big.gif

176 ms

ico_accordion_closed.gif

ico_accordion_closed.gif

193 ms

footer_background.gif

footer_background.gif

196 ms

doctor_mundi_footer.png

doctor_mundi_footer.png

214 ms

20_years_mens_health_supply.gif

20_years_mens_health_supply.gif

191 ms

ico_footer_list.gif

ico_footer_list.gif

193 ms

__utm.gif

__utm.gif

22 ms

__utm.gif

__utm.gif

14 ms

royal_mail_usps_small.gif

royal_mail_usps_small.gif

133 ms

free_shipping.gif

free_shipping.gif

148 ms

discrete_shipping_small.gif

discrete_shipping_small.gif

157 ms

money_back_small.gif

money_back_small.gif

146 ms

bsi_small.gif

bsi_small.gif

157 ms

comodo_secured_small.gif

comodo_secured_small.gif

153 ms

header_background.gif

header_background.gif

165 ms

Largerbox_logo.gif

Largerbox_logo.gif

167 ms

gray_world_map.gif

gray_world_map.gif

165 ms

downarrow.jpg

downarrow.jpg

170 ms

phone_icon.gif

phone_icon.gif

179 ms

US.gif

US.gif

182 ms

cart.gif

cart.gif

181 ms

in.php

in.php

138 ms

SEO Factors

largerbox.co 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 Largerbox.co 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 Largerbox.co 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

largerbox.co

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