Tools & Wizards About Us
digicelpacific.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

digicelpacific.com

Corporate Homepage

Page Load Speed

1.7 sec in total

First Response

180 ms

Resources Loaded

1.3 sec

Page Rendered

207 ms

digicelpacific.com screenshot

About Website

Welcome to digicelpacific.com homepage info - get ready to check Digicelpacific best content for Vanuatu right away, or after learning these important things about digicelpacific.com

Digicel, the largest mobile telecommunications operator in the Caribbean and a recent new entrant to the Central American mobile market.

Visit digicelpacific.com

Key Findings

We analyzed Digicelpacific.com page load time and found that the first response time was 180 ms and then it took 1.5 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 30% of websites can load faster.

Performance Metrics

digicelpacific.com performance score

0

Network Requests Diagram

digicelpacific.com

180 ms

jsapi

23 ms

swfobject.js

34 ms

jquery-1.3.2.js

79 ms

common.js

26 ms

Our browser made a total of 125 requests to load all elements on the main page. We found that 61% of them (76 requests) were addressed to the original Digicelpacific.com, 6% (8 requests) were made to Google.com and 6% (7 requests) were made to Digicelgroup.com. The less responsive or slowest element that took the longest time to load (212 ms) relates to the external source Digicelgroup.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 442.8 kB (61%)

Content Size

729.6 kB

After Optimization

286.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Digicelpacific.com main page is 729.6 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. 40% of websites need less resources to load. Javascripts take 419.3 kB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 51.6 kB

  • Original 63.2 kB
  • After minification 48.8 kB
  • After compression 11.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 14.3 kB, which is 23% 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 51.6 kB or 82% of the original size.

Image Optimization

-2%

Potential reduce by 3.8 kB

  • Original 159.4 kB
  • After minification 155.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. Digicelpacific images are well optimized though.

JavaScript Optimization

-74%

Potential reduce by 310.9 kB

  • Original 419.3 kB
  • After minification 315.5 kB
  • After compression 108.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 310.9 kB or 74% of the original size.

CSS Optimization

-87%

Potential reduce by 76.5 kB

  • Original 87.7 kB
  • After minification 60.6 kB
  • After compression 11.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. Digicelpacific.com needs all CSS files to be minified and compressed as it can save up to 76.5 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 87 (73%)

Requests Now

120

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

digicelpacific.com

digicelpacific.com

180 ms

jsapi

jsapi

23 ms

swfobject.js

swfobject.js

34 ms

jquery-1.3.2.js

jquery-1.3.2.js

79 ms

common.js

common.js

26 ms

thickbox.css

thickbox.css

75 ms

fonts.css

fonts.css

37 ms

home.css

home.css

75 ms

slimbox.css

slimbox.css

41 ms

moodalbox.css

moodalbox.css

45 ms

common.css

common.css

70 ms

search.css

search.css

52 ms

specific.css

specific.css

64 ms

jquery.fancybox-1.3.4.js

jquery.fancybox-1.3.4.js

187 ms

jquery.fancybox-1.3.4.css

jquery.fancybox-1.3.4.css

190 ms

wurfl.js

wurfl.js

57 ms

fonts.css

fonts.css

72 ms

screen.css

screen.css

87 ms

mootools.js

mootools.js

96 ms

slimbox.js

slimbox.js

75 ms

gtm.js

gtm.js

33 ms

ga.js

ga.js

42 ms

close.png

close.png

39 ms

logo.png

logo.png

24 ms

bubble-advert-close3_en.gif

bubble-advert-close3_en.gif

24 ms

bubble-advert-anim-en.gif

bubble-advert-anim-en.gif

89 ms

top_logo.gif

top_logo.gif

24 ms

locate_retailer_bg.gif

locate_retailer_bg.gif

38 ms

locate_retailer_bg_part.gif

locate_retailer_bg_part.gif

35 ms

locate_retailer_bg_body.gif

locate_retailer_bg_body.gif

38 ms

aia.gif

aia.gif

82 ms

atg.gif

atg.gif

88 ms

abw.gif

abw.gif

81 ms

brb.gif

brb.gif

82 ms

bmu.gif

bmu.gif

85 ms

bon.gif

bon.gif

85 ms

bvi.gif

bvi.gif

86 ms

cym.gif

cym.gif

89 ms

cur.gif

cur.gif

88 ms

dma.gif

dma.gif

89 ms

sls.gif

sls.gif

95 ms

fji.gif

fji.gif

88 ms

dfr.gif

dfr.gif

95 ms

grd.gif

grd.gif

90 ms

grp.gif

grp.gif

90 ms

pcf.gif

pcf.gif

91 ms

gya.gif

gya.gif

91 ms

hai.gif

hai.gif

94 ms

jam.gif

jam.gif

143 ms

nru.gif

nru.gif

149 ms

pan.gif

pan.gif

149 ms

png.gif

png.gif

155 ms

wsm.gif

wsm.gif

156 ms

kna.gif

kna.gif

151 ms

lca.gif

lca.gif

151 ms

vct.gif

vct.gif

152 ms

sur.gif

sur.gif

153 ms

tng.gif

tng.gif

141 ms

tto.gif

tto.gif

146 ms

conversion_async.js

conversion_async.js

55 ms

analytics.js

analytics.js

54 ms

54c97029a734704f09000022.js

54c97029a734704f09000022.js

57 ms

fbevents.js

fbevents.js

50 ms

tca.gif

tca.gif

133 ms

vtu.gif

vtu.gif

132 ms

locate_retailer_bottom_bg.gif

locate_retailer_bottom_bg.gif

132 ms

navigation_bg.gif

navigation_bg.gif

131 ms

nav_1.gif

nav_1.gif

125 ms

gtm.js

gtm.js

108 ms

fancybox-x.png

fancybox-x.png

109 ms

fancybox.png

fancybox.png

160 ms

fancybox-y.png

fancybox-y.png

172 ms

blank.gif

blank.gif

212 ms

nav_2.gif

nav_2.gif

104 ms

nav_5_bg.gif

nav_5_bg.gif

120 ms

navigation_parent.gif

navigation_parent.gif

102 ms

nav_3.gif

nav_3.gif

100 ms

nav_3_bg.gif

nav_3_bg.gif

120 ms

nav_4.gif

nav_4.gif

101 ms

nav_4_bg.gif

nav_4_bg.gif

119 ms

nav_5.gif

nav_5.gif

118 ms

sub_navigation_bg.gif

sub_navigation_bg.gif

117 ms

heading1.jpg

heading1.jpg

115 ms

heading2.jpg

heading2.jpg

144 ms

quick_links_arrow.gif

quick_links_arrow.gif

129 ms

GEN_mainimage.jpg

GEN_mainimage.jpg

128 ms

home_group_long_panel.gif

home_group_long_panel.gif

140 ms

fuo_bg.gif

fuo_bg.gif

139 ms

icon_facebook.jpg

icon_facebook.jpg

125 ms

icon_twitter.jpg

icon_twitter.jpg

142 ms

footer_bg.gif

footer_bg.gif

141 ms

105 ms

linkid.js

linkid.js

74 ms

81 ms

123 ms

124 ms

75 ms

collect

collect

26 ms

collect

collect

125 ms

collect

collect

33 ms

collect

collect

180 ms

tagjs

tagjs

46 ms

85 ms

62 ms

114 ms

130 ms

adsct

adsct

196 ms

Pug

Pug

161 ms

pixel

pixel

154 ms

114 ms

107 ms

120 ms

ga-audiences

ga-audiences

87 ms

index.php

index.php

195 ms

sd

sd

9 ms

ncm

ncm

48 ms

cb

cb

45 ms

cb

cb

9 ms

tap.php

tap.php

23 ms

cb

cb

6 ms

jquery-1.3.2.js

jquery-1.3.2.js

159 ms

27 ms

PCF_en.jpg

PCF_en.jpg

166 ms

__utm.gif

__utm.gif

27 ms

__utm.gif

__utm.gif

11 ms

SEO Factors

digicelpacific.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 Digicelpacific.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 Digicelpacific.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

digicelpacific.com

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