Tools & Wizards About Us
ifly.com screenshot

Report Summary

  • 45

    Performance

    Renders faster than
    64% of other websites

  • 86

    Accessibility

    Visual factors better than
    that of 61% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 93

    SEO

    Google-friendlier than
    83% of websites

ifly.com

Airport Guide: Flight Status, Parking, Maps, Airlines, More!

Page Load Speed

962 ms in total

First Response

10 ms

Resources Loaded

553 ms

Page Rendered

399 ms

ifly.com screenshot

About Website

Visit ifly.com now to see the best up-to-date Ifly content for United States and also check out these interesting facts you probably never knew about ifly.com

Traveler Guide to Airports and Flying: Flight Tracking, Airlines, Terminals, Security, Parking, Maps, Flyer tips, Travel with Kids, Baggage Tips

Visit ifly.com

Key Findings

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

ifly.com performance score

45

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.3 s

73/100

10%

LCP (Largest Contentful Paint)

Value2.5 s

90/100

25%

SI (Speed Index)

Value20.4 s

0/100

10%

TBT (Total Blocking Time)

Value23,300 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value73.3 s

0/100

10%

Network Requests Diagram

ifly.com

10 ms

ifly.com

15 ms

www.ifly.com

197 ms

5b710036f58a60f3.css

62 ms

polyfills-c67a75d1b6f99dc8.js

82 ms

Our browser made a total of 56 requests to load all elements on the main page. We found that 91% of them (51 requests) were addressed to the original Ifly.com, 7% (4 requests) were made to Fast.wistia.net and 2% (1 request) were made to Ezojs.com. The less responsive or slowest element that took the longest time to load (249 ms) belongs to the original domain Ifly.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 269.6 kB (49%)

Content Size

554.7 kB

After Optimization

285.0 kB

  • HTML
  • Images
  • JavaScript

In fact, the total size of Ifly.com main page is 554.7 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. 65% of websites need less resources to load. HTML takes 343.6 kB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 268.9 kB

  • Original 343.6 kB
  • After minification 343.2 kB
  • After compression 74.7 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 268.9 kB or 78% of the original size.

Image Optimization

-13%

Potential reduce by 484 B

  • Original 3.8 kB
  • After minification 3.3 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. Obviously, Ifly needs image optimization as it can save up to 484 B or 13% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-0%

Potential reduce by 243 B

  • Original 207.2 kB
  • After minification 207.2 kB
  • After compression 207.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.

Requests Breakdown

Number of requests can be reduced by 49 (92%)

Requests Now

53

After Optimization

4

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ifly.com

ifly.com

10 ms

ifly.com

ifly.com

15 ms

www.ifly.com

www.ifly.com

197 ms

5b710036f58a60f3.css

5b710036f58a60f3.css

62 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

82 ms

sa.min.js

sa.min.js

172 ms

6809-1b7fccb5a58917d1.js

6809-1b7fccb5a58917d1.js

101 ms

4707.3ca40037ab643122.js

4707.3ca40037ab643122.js

102 ms

4178.5f5d805b288f175d.js

4178.5f5d805b288f175d.js

100 ms

4693.6f0dc059a9176a15.js

4693.6f0dc059a9176a15.js

101 ms

5619.cc832396b051cbd7.js

5619.cc832396b051cbd7.js

100 ms

8984.a1f79b6b48df2173.js

8984.a1f79b6b48df2173.js

100 ms

4939.f63181c45c0d4026.js

4939.f63181c45c0d4026.js

113 ms

769.1b7a7fecfc16bd70.js

769.1b7a7fecfc16bd70.js

109 ms

6931.192a9d71fd7a43c9.js

6931.192a9d71fd7a43c9.js

110 ms

0c428ae2-88d8368466877067.js

0c428ae2-88d8368466877067.js

113 ms

1bfc9850-df1c8732e769405d.js

1bfc9850-df1c8732e769405d.js

112 ms

d7eeaac4.c1ce8b68723be727.js

d7eeaac4.c1ce8b68723be727.js

113 ms

252f366e-f8bc63d980b0e2e1.js

252f366e-f8bc63d980b0e2e1.js

175 ms

95b64a6e.b86d3186aa87ea34.js

95b64a6e.b86d3186aa87ea34.js

172 ms

8096-36b56ff773df0292.js

8096-36b56ff773df0292.js

177 ms

1216-b9b51510feee9c3a.js

1216-b9b51510feee9c3a.js

173 ms

5824-ef28344d4665ac3c.js

5824-ef28344d4665ac3c.js

180 ms

5675.c32dbc38febeec79.js

5675.c32dbc38febeec79.js

172 ms

3854.ae26580c536fbce5.js

3854.ae26580c536fbce5.js

197 ms

3455-81d77d87447c5648.js

3455-81d77d87447c5648.js

195 ms

5941-3a8e6333c7ee293f.js

5941-3a8e6333c7ee293f.js

198 ms

7661-be690809d8fd0f8f.js

7661-be690809d8fd0f8f.js

202 ms

5186-7c8752f26019bba5.js

5186-7c8752f26019bba5.js

203 ms

2028.174cc64c0a39cac8.js

2028.174cc64c0a39cac8.js

200 ms

2318-22900a55aee5eb5a.js

2318-22900a55aee5eb5a.js

206 ms

4635.da12fe905e7ac715.js

4635.da12fe905e7ac715.js

207 ms

4051.b68650d94f37a256.js

4051.b68650d94f37a256.js

207 ms

1463.7c547bf0fd5d0c5a.js

1463.7c547bf0fd5d0c5a.js

209 ms

5023.301009778f8e67b3.js

5023.301009778f8e67b3.js

210 ms

webpack-617a426fba4dce14.js

webpack-617a426fba4dce14.js

212 ms

framework-5da1132c51966f60.js

framework-5da1132c51966f60.js

213 ms

main-4c91ec4f65a74c4a.js

main-4c91ec4f65a74c4a.js

220 ms

_app-d73dea78fb2adbf7.js

_app-d73dea78fb2adbf7.js

246 ms

ne3q18ieqe

ne3q18ieqe

83 ms

75fc9c18-2a61f47d21a1bfe0.js

75fc9c18-2a61f47d21a1bfe0.js

228 ms

6261-fe07c03dee2f8de4.js

6261-fe07c03dee2f8de4.js

187 ms

7587-a02bfb609dd6d1d9.js

7587-a02bfb609dd6d1d9.js

247 ms

5217-8694cc645e9ba791.js

5217-8694cc645e9ba791.js

243 ms

9775-f6a31a6fc8ad72b1.js

9775-f6a31a6fc8ad72b1.js

165 ms

7522-37d215fdce7d524c.js

7522-37d215fdce7d524c.js

245 ms

1862-b883996a0c8a69cc.js

1862-b883996a0c8a69cc.js

247 ms

5042-7b020d8a8ced0709.js

5042-7b020d8a8ced0709.js

249 ms

3385-9c64eca188c040d0.js

3385-9c64eca188c040d0.js

247 ms

E-v1.js

E-v1.js

11 ms

swatch

swatch

10 ms

8877-ff501e272e1007f7.js

8877-ff501e272e1007f7.js

240 ms

index-f010f617f4580a7a.js

index-f010f617f4580a7a.js

241 ms

_buildManifest.js

_buildManifest.js

240 ms

_ssgManifest.js

_ssgManifest.js

242 ms

insideIframe.js

insideIframe.js

87 ms

Accessibility Review

ifly.com accessibility score

86

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

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

ifly.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Requests the notification permission on page load

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

ifly.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

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 Ifly.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 Ifly.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

ifly.com

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