Tools & Wizards About Us
ogenie.app screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

ogenie.app

India's First Conversational App|Book Flights With Ogenie App

Page Load Speed

473 ms in total

First Response

27 ms

Resources Loaded

391 ms

Page Rendered

55 ms

ogenie.app screenshot

About Website

Click here to check amazing Ogenie content for India. Otherwise, check out these important facts you probably never knew about ogenie.app

Just a voice command away, now surf & book, cancel or reschedule your flight tickets online with Ogenie's best ever known application in travel technology.

Visit ogenie.app

Key Findings

We analyzed Ogenie.app page load time and found that the first response time was 27 ms and then it took 446 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

ogenie.app performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value16.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value17.0 s

0/100

25%

SI (Speed Index)

Value16.3 s

0/100

10%

TBT (Total Blocking Time)

Value900 ms

31/100

30%

CLS (Cumulative Layout Shift)

Value0.008

100/100

15%

TTI (Time to Interactive)

Value19.5 s

2/100

10%

Network Requests Diagram

ogenie.app

27 ms

ogenietravels.com

112 ms

main.03042522.js

120 ms

main.d72c5c58.css

154 ms

Our browser made a total of 4 requests to load all elements on the main page. We found that 25% of them (1 request) were addressed to the original Ogenie.app, 75% (3 requests) were made to Ogenietravels.com. The less responsive or slowest element that took the longest time to load (154 ms) relates to the external source Ogenietravels.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.8 MB (66%)

Content Size

2.6 MB

After Optimization

891.2 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Ogenie.app main page is 2.6 MB. This result falls within a vast category (top 1 000 000) of heavyweight, probably not optimized, and thus slow loading web pages. Only a small number of websites need less resources to load. Javascripts take 2.2 MB which makes up the majority of the site volume.

HTML Optimization

-47%

Potential reduce by 396 B

  • Original 838 B
  • After minification 838 B
  • After compression 442 B

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 396 B or 47% of the original size.

JavaScript Optimization

-63%

Potential reduce by 1.4 MB

  • Original 2.2 MB
  • After minification 2.2 MB
  • After compression 799.4 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 1.4 MB or 63% of the original size.

CSS Optimization

-81%

Potential reduce by 391.0 kB

  • Original 482.3 kB
  • After minification 482.3 kB
  • After compression 91.3 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. Ogenie.app needs all CSS files to be minified and compressed as it can save up to 391.0 kB or 81% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

2

After Optimization

2

  • JavaScript
  • CSS

The browser has sent 2 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Ogenie. According to our analytics all requests are already optimized.

Network Requests Diagram

ogenie.app

ogenie.app

27 ms

ogenietravels.com

ogenietravels.com

112 ms

main.03042522.js

main.03042522.js

120 ms

main.d72c5c58.css

main.d72c5c58.css

154 ms

Accessibility Review

ogenie.app accessibility score

75

Accessibility Issues

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

Image elements do not have [alt] attributes

High

Form elements do not have associated labels

High

Links do not have a discernible name

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

ogenie.app 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

ogenie.app SEO score

77

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

High

Image elements do not have [alt] attributes

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

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 Ogenie.app 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 Ogenie.app 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

ogenie.app

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