Tools & Wizards About Us
iglobe.ca screenshot

Report Summary

  • 33

    Performance

    Renders faster than
    53% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

iglobe.ca

Game Localization In Your Culture and Language - iGlobe

Page Load Speed

3.7 sec in total

First Response

178 ms

Resources Loaded

3 sec

Page Rendered

516 ms

iglobe.ca screenshot

About Website

Visit iglobe.ca now to see the best up-to-date IGlobe content and also check out these interesting facts you probably never knew about iglobe.ca

iGlobe is your best partner. We're passionate about giving you the best services for game localization into your target market's cultural...

Visit iglobe.ca

Key Findings

We analyzed Iglobe.ca page load time and found that the first response time was 178 ms and then it took 3.5 sec to load all DOM resources and completely render a web page. This is a poor result, as 60% of websites can load faster.

Performance Metrics

iglobe.ca performance score

33

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.8 s

5/100

10%

LCP (Largest Contentful Paint)

Value10.9 s

0/100

25%

SI (Speed Index)

Value12.1 s

4/100

10%

TBT (Total Blocking Time)

Value580 ms

51/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value12.6 s

14/100

10%

Network Requests Diagram

iglobe.ca

178 ms

272lv.css

36 ms

css

51 ms

272lv.css

82 ms

272lv.css

98 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 77% of them (50 requests) were addressed to the original Iglobe.ca, 14% (9 requests) were made to Fonts.gstatic.com and 5% (3 requests) were made to Static.addtoany.com. The less responsive or slowest element that took the longest time to load (283 ms) belongs to the original domain Iglobe.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 194.6 kB (11%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iglobe.ca main page is 1.7 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. 60% of websites need less resources to load. Images take 1.1 MB which makes up the majority of the site volume.

HTML Optimization

-84%

Potential reduce by 120.8 kB

  • Original 144.3 kB
  • After minification 138.7 kB
  • After compression 23.5 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 120.8 kB or 84% of the original size.

Image Optimization

-7%

Potential reduce by 71.9 kB

  • Original 1.1 MB
  • After minification 1.0 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. IGlobe images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 1.1 kB

  • Original 250.8 kB
  • After minification 250.8 kB
  • After compression 249.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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 790 B

  • Original 213.8 kB
  • After minification 213.8 kB
  • After compression 213.0 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. Iglobe.ca has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 38 (72%)

Requests Now

53

After Optimization

15

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iglobe.ca

iglobe.ca

178 ms

272lv.css

272lv.css

36 ms

css

css

51 ms

272lv.css

272lv.css

82 ms

272lv.css

272lv.css

98 ms

272lv.css

272lv.css

99 ms

post-38.css

post-38.css

77 ms

272lv.css

272lv.css

121 ms

post-277.css

post-277.css

74 ms

272lv.css

272lv.css

109 ms

post-1674.css

post-1674.css

108 ms

post-900.css

post-900.css

112 ms

272lv.css

272lv.css

114 ms

css

css

44 ms

page.js

page.js

45 ms

272lv.js

272lv.js

159 ms

272lv.js

272lv.js

156 ms

js

js

91 ms

272lv.css

272lv.css

155 ms

style.min.js

style.min.js

155 ms

general.min.js

general.min.js

155 ms

jquery.smartmenus.min.js

jquery.smartmenus.min.js

213 ms

imagesloaded.min.js

imagesloaded.min.js

213 ms

isotope.min.js

isotope.min.js

215 ms

slick.min.js

slick.min.js

218 ms

premium-addons.min.js

premium-addons.min.js

218 ms

forms.js

forms.js

281 ms

webpack-pro.runtime.min.js

webpack-pro.runtime.min.js

280 ms

webpack.runtime.min.js

webpack.runtime.min.js

281 ms

frontend-modules.min.js

frontend-modules.min.js

282 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

280 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

282 ms

wp-polyfill.min.js

wp-polyfill.min.js

282 ms

hooks.min.js

hooks.min.js

282 ms

i18n.min.js

i18n.min.js

282 ms

frontend.min.js

frontend.min.js

283 ms

waypoints.min.js

waypoints.min.js

282 ms

core.min.js

core.min.js

283 ms

frontend.min.js

frontend.min.js

283 ms

elements-handlers.min.js

elements-handlers.min.js

283 ms

eso.Ep5bSEmr.js

eso.Ep5bSEmr.js

133 ms

logo-en-40w-1.png

logo-en-40w-1.png

80 ms

fp-bg-04b.jpg

fp-bg-04b.jpg

217 ms

banner-02a.jpg

banner-02a.jpg

218 ms

fp-icon01b.png

fp-icon01b.png

79 ms

fp-icon03a.png

fp-icon03a.png

78 ms

fp-icon06a.png

fp-icon06a.png

80 ms

fp-icon05a.png

fp-icon05a.png

82 ms

logo-zh-70.png

logo-zh-70.png

82 ms

wechat-40.png

wechat-40.png

80 ms

zhihu-40.png

zhihu-40.png

81 ms

twitter-40.png

twitter-40.png

126 ms

fb-40.png

fb-40.png

126 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw5aX8.ttf

93 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw5aX8.ttf

92 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw5aX8.ttf

168 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr6Hw5aX8.ttf

187 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Xw5aX8.ttf

186 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w5aX8.ttf

186 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w5aX8.ttf

186 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w5aX8.ttf

186 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvC73w5aX8.ttf

186 ms

fa-solid-900.woff

fa-solid-900.woff

155 ms

fa-regular-400.woff

fa-regular-400.woff

136 ms

sm.25.html

sm.25.html

74 ms

Accessibility Review

iglobe.ca accessibility score

86

Accessibility Issues

ARIA

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

[aria-*] attributes do not match their roles

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Names and labels

These are opportunities to improve the semantics of the controls in your application. This may enhance the experience for users of assistive technology, like a screen reader.

Impact

Issue

High

Links do not have a discernible name

Best Practices

iglobe.ca best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

iglobe.ca SEO score

92

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

Links are not crawlable

Mobile Friendly

Make sure your pages are mobile friendly so users don’t have to pinch or zoom in order to read the content pages. [Learn more](https://developers.google.com/search/mobile-sites/).

Impact

Issue

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

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

iglobe.ca

Open Graph data is detected on the main page of IGlobe. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: