Tools & Wizards About Us
ifonly.net screenshot

Report Summary

  • 42

    Performance

    Renders faster than
    61% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 41% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 85

    SEO

    Google-friendlier than
    55% of websites

ifonly.net

If Only, Travel Made Beautiful. Luxury tour operator.

Page Load Speed

3.2 sec in total

First Response

186 ms

Resources Loaded

2.5 sec

Page Rendered

514 ms

ifonly.net screenshot

About Website

Click here to check amazing If Only content for United Kingdom. Otherwise, check out these important facts you probably never knew about ifonly.net

Luxury, tailormade holidays in the Indian Ocean, Arabia, Asia, Australasia, Caribbean, Mexico, USA, Canada, India & Sri Lanka

Visit ifonly.net

Key Findings

We analyzed Ifonly.net page load time and found that the first response time was 186 ms and then it took 3 sec to load all DOM resources and completely render a web page. This is a poor result, as 55% of websites can load faster.

Performance Metrics

ifonly.net performance score

42

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value9.9 s

0/100

25%

SI (Speed Index)

Value7.5 s

27/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value9.4 s

30/100

10%

Network Requests Diagram

ifonly.net

186 ms

www.ifonly.net

892 ms

gtm.js

93 ms

masterstylesheet.css

354 ms

lec2gez.css

129 ms

Our browser made a total of 38 requests to load all elements on the main page. We found that 45% of them (17 requests) were addressed to the original Ifonly.net, 18% (7 requests) were made to Use.typekit.net and 5% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (892 ms) belongs to the original domain Ifonly.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 366.6 kB (34%)

Content Size

1.1 MB

After Optimization

721.6 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Ifonly.net main page is 1.1 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. 55% of websites need less resources to load. Images take 474.5 kB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 235.1 kB

  • Original 294.0 kB
  • After minification 263.6 kB
  • After compression 58.8 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 235.1 kB or 80% of the original size.

Image Optimization

-2%

Potential reduce by 11.4 kB

  • Original 474.5 kB
  • After minification 463.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. If Only images are well optimized though.

JavaScript Optimization

-36%

Potential reduce by 103.9 kB

  • Original 288.4 kB
  • After minification 288.4 kB
  • After compression 184.5 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 103.9 kB or 36% of the original size.

CSS Optimization

-52%

Potential reduce by 16.2 kB

  • Original 31.3 kB
  • After minification 31.3 kB
  • After compression 15.1 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. Ifonly.net needs all CSS files to be minified and compressed as it can save up to 16.2 kB or 52% of the original size.

Requests Breakdown

Number of requests can be reduced by 15 (56%)

Requests Now

27

After Optimization

12

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

ifonly.net

ifonly.net

186 ms

www.ifonly.net

www.ifonly.net

892 ms

gtm.js

gtm.js

93 ms

masterstylesheet.css

masterstylesheet.css

354 ms

lec2gez.css

lec2gez.css

129 ms

p.css

p.css

275 ms

js

js

85 ms

analytics.js

analytics.js

58 ms

fbevents.js

fbevents.js

28 ms

WebResource.axd

WebResource.axd

244 ms

ScriptResource.axd

ScriptResource.axd

251 ms

ScriptResource.axd

ScriptResource.axd

343 ms

uc.js

uc.js

162 ms

css

css

175 ms

sitesearch360-v13.min.js

sitesearch360-v13.min.js

164 ms

yall.min.js

yall.min.js

357 ms

polyfill.min.js

polyfill.min.js

377 ms

io.js

io.js

460 ms

collect

collect

136 ms

ukflag.svg

ukflag.svg

524 ms

ifonly-logo.svg

ifonly-logo.svg

468 ms

atol.svg

atol.svg

464 ms

abta.svg

abta.svg

465 ms

iata.svg

iata.svg

466 ms

ieFlag.png

ieFlag.png

548 ms

d

d

32 ms

d

d

76 ms

d

d

107 ms

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

flUhRq6tzZclQEJ-Vdg-IuiaDsNZ.ttf

144 ms

d

d

110 ms

d

d

109 ms

d

d

110 ms

sprite.svg

sprite.svg

126 ms

ss360-unibox-v13.chunk.27665f6cc18723c8c279.js

ss360-unibox-v13.chunk.27665f6cc18723c8c279.js

47 ms

ukflag.svg

ukflag.svg

100 ms

ieFlag.png

ieFlag.png

95 ms

121013

121013

420 ms

122113

122113

843 ms

Accessibility Review

ifonly.net accessibility score

75

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

High

Some elements have a [tabindex] value greater than 0

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.

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

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

ifonly.net 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

Page has valid source maps

SEO Factors

ifonly.net 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

    N/A

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Ifonly.net can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and neither this language nor any other was claimed in <html> or <meta> tags. Our system also found out that Ifonly.net 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

ifonly.net

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