Tools & Wizards About Us
wingie.com screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 70

    Accessibility

    Visual factors better than
    that of 35% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 98

    SEO

    Google-friendlier than
    92% of websites

wingie.com

Cheap Flights, Find Cheap Airline Tickets & Airfare Deals | Wingie

Page Load Speed

1.4 sec in total

First Response

30 ms

Resources Loaded

948 ms

Page Rendered

444 ms

wingie.com screenshot

About Website

Visit wingie.com now to see the best up-to-date Wingie content for Saudi Arabia and also check out these interesting facts you probably never knew about wingie.com

Compare and find cheap flights and save on flight tickets. Book and buy tickets online securely and easily. Instantly compare flights from over 300 airlines to book the best deal quickly and securely ...

Visit wingie.com

Key Findings

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

wingie.com performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

42/100

10%

LCP (Largest Contentful Paint)

Value12.0 s

0/100

25%

SI (Speed Index)

Value6.0 s

47/100

10%

TBT (Total Blocking Time)

Value3,310 ms

2/100

30%

CLS (Cumulative Layout Shift)

Value0.003

100/100

15%

TTI (Time to Interactive)

Value16.4 s

5/100

10%

Network Requests Diagram

wingie.com

30 ms

wingie.com

170 ms

www.wingie.com

161 ms

eac6d6e9937b93a0.css

93 ms

polyfills-c67a75d1b6f99dc8.js

139 ms

Our browser made a total of 53 requests to load all elements on the main page. We found that 53% of them (28 requests) were addressed to the original Wingie.com, 34% (18 requests) were made to Cdn.wingie.com and 11% (6 requests) were made to Cdn2.enuygun.com. The less responsive or slowest element that took the longest time to load (595 ms) belongs to the original domain Wingie.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 340.4 kB (22%)

Content Size

1.5 MB

After Optimization

1.2 MB

  • HTML
  • Images

In fact, the total size of Wingie.com main page is 1.5 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

-77%

Potential reduce by 330.3 kB

  • Original 427.3 kB
  • After minification 427.2 kB
  • After compression 97.1 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 330.3 kB or 77% of the original size.

Image Optimization

-1%

Potential reduce by 10.2 kB

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

Requests Breakdown

Number of requests can be reduced by 18 (36%)

Requests Now

50

After Optimization

32

  • Images
  • JavaScript
  • CSS

The browser has sent 50 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Wingie. 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 as a result speed up the page load time.

Network Requests Diagram

wingie.com

wingie.com

30 ms

wingie.com

wingie.com

170 ms

www.wingie.com

www.wingie.com

161 ms

eac6d6e9937b93a0.css

eac6d6e9937b93a0.css

93 ms

polyfills-c67a75d1b6f99dc8.js

polyfills-c67a75d1b6f99dc8.js

139 ms

504.5cfd404bf77accd6.js

504.5cfd404bf77accd6.js

168 ms

377.54b9b3a8a4315ff4.js

377.54b9b3a8a4315ff4.js

172 ms

345.2cee899efd5f28d7.js

345.2cee899efd5f28d7.js

173 ms

82.4c99927fdaf92506.js

82.4c99927fdaf92506.js

174 ms

629.060d58b65f6bc208.js

629.060d58b65f6bc208.js

167 ms

308.d5e987c94bcbcaf8.js

308.d5e987c94bcbcaf8.js

172 ms

975.5c00d928692a8afe.js

975.5c00d928692a8afe.js

196 ms

webpack-55dd874136b32ab3.js

webpack-55dd874136b32ab3.js

195 ms

framework-10fac88913917d91.js

framework-10fac88913917d91.js

191 ms

main-a5de00c402ddc488.js

main-a5de00c402ddc488.js

202 ms

_app-5ff6955741682c28.js

_app-5ff6955741682c28.js

208 ms

41-7f0c32ab2e18bd8b.js

41-7f0c32ab2e18bd8b.js

221 ms

734-ea34d63b7df041f7.js

734-ea34d63b7df041f7.js

219 ms

%5B%5B...slug%5D%5D-6a4c05a40c619fec.js

%5B%5B...slug%5D%5D-6a4c05a40c619fec.js

226 ms

_buildManifest.js

_buildManifest.js

224 ms

_ssgManifest.js

_ssgManifest.js

225 ms

wingie-qr-49027.png

wingie-qr-49027.png

55 ms

lon-1-v-19310.jpg

lon-1-v-19310.jpg

32 ms

hav-1-v-19310.jpg

hav-1-v-19310.jpg

34 ms

sal-1-v-19310.jpg

sal-1-v-19310.jpg

149 ms

gdl-1-v-19310.jpg

gdl-1-v-19310.jpg

141 ms

tlv-1-v-19310.jpg

tlv-1-v-19310.jpg

141 ms

sju-1-v-19310.jpg

sju-1-v-19310.jpg

480 ms

mex-1-v-19310.jpg

mex-1-v-19310.jpg

140 ms

par-1-v-19310.jpg

par-1-v-19310.jpg

51 ms

mia-1-v-19310.jpg

mia-1-v-19310.jpg

67 ms

orl-1-v-19310.jpg

orl-1-v-19310.jpg

138 ms

lax-1-v-19310.jpg

lax-1-v-19310.jpg

278 ms

las-1-v-19310.jpg

las-1-v-19310.jpg

277 ms

lax-2-v-19310.jpg

lax-2-v-19310.jpg

319 ms

orl-2-v-19310.jpg

orl-2-v-19310.jpg

595 ms

atl-1-v-19310.jpg

atl-1-v-19310.jpg

278 ms

las-2-v-19310.jpg

las-2-v-19310.jpg

372 ms

AA-v-19310.svg

AA-v-19310.svg

350 ms

DL-v-19310.svg

DL-v-19310.svg

283 ms

UA-v-19310.svg

UA-v-19310.svg

305 ms

AS-v-19310.svg

AS-v-19310.svg

418 ms

B6-v-19310.svg

B6-v-19310.svg

344 ms

HA-v-19310.svg

HA-v-19310.svg

364 ms

NK-v-19310.svg

NK-v-19310.svg

369 ms

WN-v-19310.svg

WN-v-19310.svg

383 ms

wingie-app-banner-61676.png

wingie-app-banner-61676.png

135 ms

wingie-qr-48797.png

wingie-qr-48797.png

32 ms

google-play-wingie-48798.png

google-play-wingie-48798.png

33 ms

apple-store-wingie-48799.png

apple-store-wingie-48799.png

38 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

61 ms

homepages-summer-bg-59600.webp

homepages-summer-bg-59600.webp

162 ms

main.js

main.js

10 ms

Accessibility Review

wingie.com accessibility score

70

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

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

Buttons do not have an accessible name

High

Form elements do not have associated labels

High

Links do not have a discernible name

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.

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a valid value for its [lang] attribute.

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

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

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

wingie.com SEO score

98

Search Engine Optimization Advices

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

    US

  • Encoding

    UTF-8

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

wingie.com

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