Tools & Wizards About Us
iworld.com screenshot

Report Summary

  • 27

    Performance

    Renders faster than
    46% of other websites

  • 78

    Accessibility

    Visual factors better than
    that of 45% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

iworld.com

iWorld - All migration services on one marketplace!

Page Load Speed

7.7 sec in total

First Response

46 ms

Resources Loaded

7.3 sec

Page Rendered

375 ms

iworld.com screenshot

About Website

Welcome to iworld.com homepage info - get ready to check IWorld best content for United States right away, or after learning these important things about iworld.com

The first international marketplace for immigration services iworld.com: immigration, investment, real estate, travel, work, business, study abroad

Visit iworld.com

Key Findings

We analyzed Iworld.com page load time and found that the first response time was 46 ms and then it took 7.7 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

iworld.com performance score

27

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.4 s

98/100

10%

LCP (Largest Contentful Paint)

Value10.3 s

0/100

25%

SI (Speed Index)

Value12.4 s

3/100

10%

TBT (Total Blocking Time)

Value3,590 ms

1/100

30%

CLS (Cumulative Layout Shift)

Value0.005

100/100

15%

TTI (Time to Interactive)

Value13.1 s

12/100

10%

Network Requests Diagram

iworld.com

46 ms

iworld.com

58 ms

en

4657 ms

gtm.js

62 ms

polyfills-5cd94c89d3acac5f.js

176 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 13% of them (10 requests) were addressed to the original Iworld.com, 48% (38 requests) were made to Static.iworld.com and 14% (11 requests) were made to Dynamic.iworld.com. The less responsive or slowest element that took the longest time to load (4.7 sec) belongs to the original domain Iworld.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 187.3 kB (15%)

Content Size

1.3 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-78%

Potential reduce by 154.5 kB

  • Original 199.0 kB
  • After minification 198.6 kB
  • After compression 44.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 154.5 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 482.1 kB
  • After minification 482.1 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. IWorld images are well optimized though.

JavaScript Optimization

-7%

Potential reduce by 32.7 kB

  • Original 494.7 kB
  • After minification 494.7 kB
  • After compression 462.0 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 145 B

  • Original 85.2 kB
  • After minification 85.2 kB
  • After compression 85.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. Iworld.com has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 43 (62%)

Requests Now

69

After Optimization

26

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iworld.com

iworld.com

46 ms

iworld.com

iworld.com

58 ms

en

en

4657 ms

gtm.js

gtm.js

62 ms

polyfills-5cd94c89d3acac5f.js

polyfills-5cd94c89d3acac5f.js

176 ms

1413-a70f385082f73e23.js

1413-a70f385082f73e23.js

186 ms

9309.4026bd0daf9591a8.js

9309.4026bd0daf9591a8.js

416 ms

webpack-7de068c5cdd365a5.js

webpack-7de068c5cdd365a5.js

416 ms

framework-58923057365dff13.js

framework-58923057365dff13.js

890 ms

main-3af67e8b31c4ed75.js

main-3af67e8b31c4ed75.js

415 ms

_app-df06c72a73a17f6b.js

_app-df06c72a73a17f6b.js

444 ms

29107295-9c7490dd9b7c17fb.js

29107295-9c7490dd9b7c17fb.js

870 ms

140-96ff56f47dd6cca5.js

140-96ff56f47dd6cca5.js

654 ms

9889-9e726ce88f235535.js

9889-9e726ce88f235535.js

638 ms

1053-b501f166a1b6c636.js

1053-b501f166a1b6c636.js

639 ms

9788-d7dfd5f17d4b9871.js

9788-d7dfd5f17d4b9871.js

650 ms

6849-fc9d68136b2aba9b.js

6849-fc9d68136b2aba9b.js

791 ms

8304-e27926390c862464.js

8304-e27926390c862464.js

674 ms

241-e33818b460b35624.js

241-e33818b460b35624.js

671 ms

6289-48b5c6cefc4f8ca5.js

6289-48b5c6cefc4f8ca5.js

675 ms

9815-c42b78e954ea85f5.js

9815-c42b78e954ea85f5.js

813 ms

6519-ac7758b2b9a560a4.js

6519-ac7758b2b9a560a4.js

813 ms

2734-9b6a007318a288f9.js

2734-9b6a007318a288f9.js

813 ms

index-913fa38e8afd6420.js

index-913fa38e8afd6420.js

812 ms

_buildManifest.js

_buildManifest.js

865 ms

_ssgManifest.js

_ssgManifest.js

869 ms

_middlewareManifest.js

_middlewareManifest.js

872 ms

gb.svg

gb.svg

864 ms

logo.svg

logo.svg

870 ms

js

js

56 ms

analytics.js

analytics.js

198 ms

tag.js

tag.js

302 ms

fbevents.js

fbevents.js

301 ms

image

image

1031 ms

email-decode.min.js

email-decode.min.js

248 ms

image

image

1008 ms

image

image

844 ms

image

image

1006 ms

image

image

877 ms

image

image

1006 ms

image

image

1371 ms

image

image

1272 ms

image

image

1325 ms

image

image

1321 ms

image

image

1323 ms

arrow-right-accent.svg

arrow-right-accent.svg

468 ms

arrow-right-next.svg

arrow-right-next.svg

481 ms

subscribeBgImg.jpg

subscribeBgImg.jpg

695 ms

hor-bg.webp

hor-bg.webp

480 ms

hor-bg2.webp

hor-bg2.webp

479 ms

mail.svg

mail.svg

481 ms

flag.svg

flag.svg

705 ms

whiteLogo.svg

whiteLogo.svg

710 ms

MIRSATORI.png

MIRSATORI.png

714 ms

collect

collect

251 ms

1560970747599349

1560970747599349

190 ms

advert.gif

advert.gif

890 ms

collect

collect

30 ms

js

js

37 ms

ga-audiences

ga-audiences

215 ms

abd99e7be5045a74.css

abd99e7be5045a74.css

117 ms

f8e62f7207930ecc.css

f8e62f7207930ecc.css

62 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw9aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtZ6Hw9aXw.woff

56 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCtr6Hw9aXw.woff

86 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw9aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCs16Hw9aXw.woff

123 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w9aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCu173w9aXw.woff

123 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCuM73w9aXw.woff

124 ms

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w9aXw.woff

JTUHjIg1_i6t8kCHKm4532VJOt5-QNFgpCvr73w9aXw.woff

123 ms

mail.svg

mail.svg

65 ms

1

1

360 ms

c5c18977381ae59d.css

c5c18977381ae59d.css

57 ms

arrow-right-accent.svg

arrow-right-accent.svg

54 ms

arrow-right-next.svg

arrow-right-next.svg

31 ms

subscribeBgImg.jpg

subscribeBgImg.jpg

428 ms

1

1

293 ms

d6e73ccf6c988950.css

d6e73ccf6c988950.css

23 ms

hor-bg.webp

hor-bg.webp

58 ms

hor-bg2.webp

hor-bg2.webp

434 ms

sync_cookie_image_decide

sync_cookie_image_decide

144 ms

sync_cookie_image_decide

sync_cookie_image_decide

144 ms

Accessibility Review

iworld.com accessibility score

78

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

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

High

[aria-*] attributes do not have valid values

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.

Best Practices

iworld.com best practices score

92

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

iworld.com SEO score

93

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

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

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 Iworld.com 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 Iworld.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

iworld.com

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