Tools & Wizards About Us
hotelforex.com screenshot

Report Summary

  • 10

    Performance

    Renders faster than
    23% of other websites

  • 80

    Accessibility

    Visual factors better than
    that of 49% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

hotelforex.com

HotelForex.com | Official Site | Choose your Hotel & Haggle Now!

Page Load Speed

3.8 sec in total

First Response

58 ms

Resources Loaded

3.6 sec

Page Rendered

76 ms

hotelforex.com screenshot

About Website

Welcome to hotelforex.com homepage info - get ready to check Hotel Forex best content for Turkey right away, or after learning these important things about hotelforex.com

You think you can't haggle Hotel rates? Choose your Hotel and start haggling! Haggle Now! HotelForex.com

Visit hotelforex.com

Key Findings

We analyzed Hotelforex.com page load time and found that the first response time was 58 ms and then it took 3.7 sec to load all DOM resources and completely render a web page. This is a poor result, as 65% of websites can load faster.

Performance Metrics

hotelforex.com performance score

10

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.2 s

43/100

10%

LCP (Largest Contentful Paint)

Value10.6 s

0/100

25%

SI (Speed Index)

Value9.4 s

12/100

10%

TBT (Total Blocking Time)

Value1,780 ms

10/100

30%

CLS (Cumulative Layout Shift)

Value0.648

9/100

15%

TTI (Time to Interactive)

Value18.9 s

3/100

10%

Network Requests Diagram

hotelforex.com

58 ms

en

709 ms

css2

24 ms

bootstrap.min.css

285 ms

owl.carousel.min.css

292 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 89% of them (67 requests) were addressed to the original Hotelforex.com, 7% (5 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Fonts.googleapis.com. The less responsive or slowest element that took the longest time to load (1.8 sec) belongs to the original domain Hotelforex.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 202.8 kB (23%)

Content Size

878.5 kB

After Optimization

675.7 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hotelforex.com main page is 878.5 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. 60% of websites need less resources to load. Javascripts take 561.4 kB which makes up the majority of the site volume.

HTML Optimization

-61%

Potential reduce by 111.8 kB

  • Original 184.0 kB
  • After minification 179.7 kB
  • After compression 72.2 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 111.8 kB or 61% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 5.2 kB
  • After minification 5.2 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. Hotel Forex images are well optimized though.

JavaScript Optimization

-13%

Potential reduce by 74.8 kB

  • Original 561.4 kB
  • After minification 561.4 kB
  • After compression 486.7 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 74.8 kB or 13% of the original size.

CSS Optimization

-13%

Potential reduce by 16.3 kB

  • Original 127.9 kB
  • After minification 127.9 kB
  • After compression 111.6 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. Hotelforex.com needs all CSS files to be minified and compressed as it can save up to 16.3 kB or 13% of the original size.

Requests Breakdown

Number of requests can be reduced by 55 (81%)

Requests Now

68

After Optimization

13

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hotelforex.com

hotelforex.com

58 ms

en

en

709 ms

css2

css2

24 ms

bootstrap.min.css

bootstrap.min.css

285 ms

owl.carousel.min.css

owl.carousel.min.css

292 ms

nouislider.min.css

nouislider.min.css

293 ms

daterangepicker.css

daterangepicker.css

290 ms

jquery.fancybox.min.css

jquery.fancybox.min.css

282 ms

animate.min.css

animate.min.css

521 ms

leaflet.css

leaflet.css

551 ms

MarkerCluster.css

MarkerCluster.css

561 ms

MarkerCluster.Default.css

MarkerCluster.Default.css

565 ms

waitMe.css

waitMe.css

567 ms

style.css

style.css

568 ms

logo-hx_color.svg

logo-hx_color.svg

721 ms

tursab-header.png

tursab-header.png

724 ms

logo-hx_white.svg

logo-hx_white.svg

778 ms

tursab-md.png

tursab-md.png

694 ms

%7B%7Bitem.image%7D%7D

%7B%7Bitem.image%7D%7D

1243 ms

email-decode.min.js

email-decode.min.js

402 ms

jquery.min.js

jquery.min.js

608 ms

mobile-detect.js

mobile-detect.js

797 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

804 ms

lodash.min.js

lodash.min.js

870 ms

moment.js

moment.js

873 ms

tr.js

tr.js

881 ms

en-au.js

en-au.js

1038 ms

de.js

de.js

1041 ms

ru.js

ru.js

1141 ms

nl.js

nl.js

1136 ms

daterangepicker.js

daterangepicker.js

1149 ms

angular.min.js

angular.min.js

1277 ms

angular-cookies.min.js

angular-cookies.min.js

1276 ms

angular-filter.js

angular-filter.js

1403 ms

angular-cache.min.js

angular-cache.min.js

1405 ms

owl.carousel.min.js

owl.carousel.min.js

1414 ms

angular-owl-carousel-2.js

angular-owl-carousel-2.js

1423 ms

jquery.validate.min.js

jquery.validate.min.js

1538 ms

vcd15cbe7772f49c399c6a5babf22c1241717689176015

vcd15cbe7772f49c399c6a5babf22c1241717689176015

68 ms

messages_en.min.js

messages_en.min.js

1534 ms

additional-methods.min.js

additional-methods.min.js

1649 ms

nouislider.min.js

nouislider.min.js

1646 ms

ui-bootstrap-tpls.js

ui-bootstrap-tpls.js

1657 ms

jquery.fancybox.min.js

jquery.fancybox.min.js

1664 ms

jquery.inputmask.bundle.js

jquery.inputmask.bundle.js

1751 ms

inputmask.date.extensions.js

inputmask.date.extensions.js

1526 ms

typeahead.bundle.min.js

typeahead.bundle.min.js

1648 ms

leaflet.js

leaflet.js

1661 ms

leaflet.markercluster.js

leaflet.markercluster.js

1660 ms

waitMe.js

waitMe.js

1658 ms

site.js

site.js

1622 ms

KFOmCnqEu92Fr1Me5Q.ttf

KFOmCnqEu92Fr1Me5Q.ttf

19 ms

KFOlCnqEu92Fr1MmEU9vAw.ttf

KFOlCnqEu92Fr1MmEU9vAw.ttf

31 ms

KFOlCnqEu92Fr1MmSU5vAw.ttf

KFOlCnqEu92Fr1MmSU5vAw.ttf

47 ms

KFOlCnqEu92Fr1MmWUlvAw.ttf

KFOlCnqEu92Fr1MmWUlvAw.ttf

42 ms

KFOlCnqEu92Fr1MmYUtvAw.ttf

KFOlCnqEu92Fr1MmYUtvAw.ttf

47 ms

signalr.min.js

signalr.min.js

1620 ms

app.js

app.js

1642 ms

filters.js

filters.js

1672 ms

factories.js

factories.js

1624 ms

controllers.js

controllers.js

1625 ms

directives.js

directives.js

1650 ms

rocket-loader.min.js

rocket-loader.min.js

1234 ms

footer-logo-tursab.svg

footer-logo-tursab.svg

1397 ms

footer-logo-iyzico.svg

footer-logo-iyzico.svg

1586 ms

footer-logo-mastercard.svg

footer-logo-mastercard.svg

1591 ms

footer-logo-visa.svg

footer-logo-visa.svg

1611 ms

footer-logo-amex.svg

footer-logo-amex.svg

1452 ms

footer-logo-troy.svg

footer-logo-troy.svg

1465 ms

gtm.js

gtm.js

74 ms

jquery.min.js

jquery.min.js

15 ms

mobile-detect.js

mobile-detect.js

10 ms

bootstrap.bundle.min.js

bootstrap.bundle.min.js

9 ms

lodash.min.js

lodash.min.js

9 ms

moment.js

moment.js

23 ms

Accessibility Review

hotelforex.com accessibility score

80

Accessibility Issues

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

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.

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

hotelforex.com best practices score

75

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

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

hotelforex.com SEO score

83

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

High

robots.txt is not valid

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Hotelforex.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 Hotelforex.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

hotelforex.com

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