Tools & Wizards About Us
iway.io screenshot

Report Summary

  • 38

    Performance

    Renders faster than
    57% of other websites

  • 89

    Accessibility

    Visual factors better than
    that of 71% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

iway.io

Private car service to and from 600 airports worldwide | i’way

Page Load Speed

5.8 sec in total

First Response

213 ms

Resources Loaded

5.3 sec

Page Rendered

288 ms

iway.io screenshot

About Website

Welcome to iway.io homepage info - get ready to check I Way best content right away, or after learning these important things about iway.io

Transfers in 120 countries are available online. Any types of vehicles. Meet & Greet at the airport. 1 hour of free waiting time after landing. Book a transfer online and enjoy your trip

Visit iway.io

Key Findings

We analyzed Iway.io page load time and found that the first response time was 213 ms and then it took 5.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

iway.io performance score

38

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.9 s

53/100

10%

LCP (Largest Contentful Paint)

Value7.1 s

6/100

25%

SI (Speed Index)

Value6.4 s

40/100

10%

TBT (Total Blocking Time)

Value780 ms

38/100

30%

CLS (Cumulative Layout Shift)

Value0.045

99/100

15%

TTI (Time to Interactive)

Value13.0 s

13/100

10%

Network Requests Diagram

iway.io

213 ms

iway.io

1277 ms

css2

31 ms

intlTelInput.css

270 ms

flex.css

495 ms

Our browser made a total of 80 requests to load all elements on the main page. We found that 85% of them (68 requests) were addressed to the original Iway.io, 4% (3 requests) were made to Fonts.gstatic.com and 3% (2 requests) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (2.3 sec) belongs to the original domain Iway.io.

Page Optimization Overview & Recommendations

Page size can be reduced by 214.7 kB (13%)

Content Size

1.7 MB

After Optimization

1.5 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Iway.io 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. 40% of websites need less resources to load. Images take 997.7 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 68.2 kB

  • Original 87.7 kB
  • After minification 73.4 kB
  • After compression 19.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. This page needs HTML code to be minified as it can gain 14.3 kB, which is 16% 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 68.2 kB or 78% of the original size.

Image Optimization

-1%

Potential reduce by 5.1 kB

  • Original 997.7 kB
  • After minification 992.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. I Way images are well optimized though.

JavaScript Optimization

-23%

Potential reduce by 136.4 kB

  • Original 581.3 kB
  • After minification 581.3 kB
  • After compression 444.9 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 136.4 kB or 23% of the original size.

CSS Optimization

-19%

Potential reduce by 5.0 kB

  • Original 26.0 kB
  • After minification 26.0 kB
  • After compression 20.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. Iway.io needs all CSS files to be minified and compressed as it can save up to 5.0 kB or 19% of the original size.

Requests Breakdown

Number of requests can be reduced by 37 (53%)

Requests Now

70

After Optimization

33

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

iway.io

iway.io

213 ms

iway.io

iway.io

1277 ms

css2

css2

31 ms

intlTelInput.css

intlTelInput.css

270 ms

flex.css

flex.css

495 ms

slick.css

slick.css

440 ms

base.css

base.css

405 ms

main-page.css

main-page.css

523 ms

identification-widget.css

identification-widget.css

411 ms

libphonenumber-js-1.10.14.min.js

libphonenumber-js-1.10.14.min.js

785 ms

logo-iway_gray.svg

logo-iway_gray.svg

631 ms

app-store-icon.svg

app-store-icon.svg

679 ms

google-play-icon.svg

google-play-icon.svg

702 ms

style.css

style.css

700 ms

messageCookie.js

messageCookie.js

735 ms

jquery-1.8.3.min.js

jquery-1.8.3.min.js

1107 ms

jquery-ui-1.9.min.js

jquery-ui-1.9.min.js

1308 ms

slick.min.js

slick.min.js

974 ms

iwayTimeWidget.js

iwayTimeWidget.js

918 ms

functions.js

functions.js

1212 ms

iwayWidgets.flex_build.js

iwayWidgets.flex_build.js

1538 ms

intlTelInput.js

intlTelInput.js

1381 ms

route.js

route.js

1276 ms

base.js

base.js

1379 ms

script.js

script.js

1473 ms

reviewsWidget.css

reviewsWidget.css

1485 ms

gridify.min.js

gridify.min.js

1624 ms

reviewsWidget.js

reviewsWidget.js

1633 ms

css

css

14 ms

app-store-icon_gray.svg

app-store-icon_gray.svg

1093 ms

google-play-icon_gray.svg

google-play-icon_gray.svg

1211 ms

carphoto_standard.png

carphoto_standard.png

1291 ms

carphoto_comfort.png

carphoto_comfort.png

1341 ms

carphoto_business.png

carphoto_business.png

1281 ms

carphoto_premium.png

carphoto_premium.png

1472 ms

carphoto_minivan.png

carphoto_minivan.png

1372 ms

carphoto_micro.png

carphoto_micro.png

1620 ms

advantage_1_usd.svg

advantage_1_usd.svg

1498 ms

advantage_2.svg

advantage_2.svg

1542 ms

advantage_3.svg

advantage_3.svg

1550 ms

advantage_4.svg

advantage_4.svg

1591 ms

feature_1.svg

feature_1.svg

1724 ms

feature_2.svg

feature_2.svg

1711 ms

feature_3.svg

feature_3.svg

1797 ms

feature_4.svg

feature_4.svg

1799 ms

app_store_en.png

app_store_en.png

1798 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuLyfMZg.ttf

30 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuGKYMZg.ttf

38 ms

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

UcCO3FwrK3iLTeHuS_fvQtMwCp50KnMw2boKoduKmMEVuFuYMZg.ttf

50 ms

Inter-Regular.woff

Inter-Regular.woff

2121 ms

Inter-Medium.woff

Inter-Medium.woff

2168 ms

Inter-SemiBold.woff

Inter-SemiBold.woff

2135 ms

Inter-Bold.woff

Inter-Bold.woff

2227 ms

google_play_en.png

google_play_en.png

1814 ms

mockup_en.png

mockup_en.png

1728 ms

arrow_right.svg

arrow_right.svg

1845 ms

partnership.jpg

partnership.jpg

2253 ms

partner-phptravels.png

partner-phptravels.png

1906 ms

partner-s7.png

partner-s7.png

1760 ms

partner-atharva.png

partner-atharva.png

1771 ms

partner-global-innovations.png

partner-global-innovations.png

1765 ms

partner-netstorming.svg

partner-netstorming.svg

1811 ms

partner-travelcarma.png

partner-travelcarma.png

1805 ms

master-card.svg

master-card.svg

1821 ms

visa.svg

visa.svg

1827 ms

utils.js

utils.js

1947 ms

5_1440.jpg

5_1440.jpg

2024 ms

partnership.jpg

partnership.jpg

2094 ms

fbevents.js

fbevents.js

46 ms

analytics.js

analytics.js

85 ms

watch.js

watch.js

40 ms

social-facebook.svg

social-facebook.svg

1764 ms

collect

collect

15 ms

social-instagram.svg

social-instagram.svg

1797 ms

collect

collect

42 ms

js

js

83 ms

ga-audiences

ga-audiences

76 ms

social-linkedin.svg

social-linkedin.svg

1711 ms

prev-icon.svg

prev-icon.svg

1888 ms

next-icon.svg

next-icon.svg

1916 ms

Accessibility Review

iway.io accessibility score

89

Accessibility Issues

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.

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

Image elements do not have [alt] attributes

Best Practices

iway.io best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Missing source maps for large first-party JavaScript

SEO Factors

iway.io SEO score

85

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

Content Best Practices

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

Impact

Issue

High

Image elements do not have [alt] attributes

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 Iway.io 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 Iway.io 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

iway.io

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