4.8 sec in total
1.1 sec
3.3 sec
371 ms
Click here to check amazing Instantbreaks content. Otherwise, check out these important facts you probably never knew about instantbreaks.com
Instant Breaks has been helping people to plan and organise their perfect trips for over 36 years, including our speciality destinations such as Disneyland Paris, Lapland and Belmond day trips, of whi...
Visit instantbreaks.comWe analyzed Instantbreaks.com page load time and found that the first response time was 1.1 sec 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.
instantbreaks.com performance score
name
value
score
weighting
Value2.5 s
66/100
10%
Value9.0 s
1/100
25%
Value6.1 s
44/100
10%
Value780 ms
38/100
30%
Value0.893
3/100
15%
Value15.8 s
6/100
10%
1129 ms
805 ms
159 ms
246 ms
31 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 89% of them (54 requests) were addressed to the original Instantbreaks.com, 5% (3 requests) were made to Googletagmanager.com and 2% (1 request) were made to Code.jquery.com. The less responsive or slowest element that took the longest time to load (1.1 sec) belongs to the original domain Instantbreaks.com.
Page size can be reduced by 134.8 kB (10%)
1.4 MB
1.3 MB
In fact, the total size of Instantbreaks.com main page is 1.4 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.2 MB which makes up the majority of the site volume.
Potential reduce by 63.4 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 63.4 kB or 82% of the original size.
Potential reduce by 7.8 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. Instantbreaks images are well optimized though.
Potential reduce by 21.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 21.4 kB or 30% of the original size.
Potential reduce by 42.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. Instantbreaks.com needs all CSS files to be minified and compressed as it can save up to 42.1 kB or 52% of the original size.
Number of requests can be reduced by 11 (19%)
58
47
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Instantbreaks. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and as a result speed up the page load time.
instantbreaks.com
1129 ms
www.instantbreaks.com
805 ms
bootstrap.min.css
159 ms
disney-styles.css
246 ms
jquery-1.11.0.js
31 ms
bootstrap.min.js
346 ms
cookieconsent.js
496 ms
bootstrap-datepicker.js
575 ms
moment.min.js
717 ms
popper.min.js
652 ms
font-awesome.css
662 ms
js
135 ms
fbevents.js
103 ms
gtm.js
89 ms
hotjar-3082598.js
239 ms
instant-breaks-logo-web.png
540 ms
disneyland-paris-nav.jpg
498 ms
disney-world-florida-nav.jpg
499 ms
disney-cruise-nav.jpg
540 ms
lapland-1-day-trips-nav.jpg
541 ms
lapland-3-day-trips-nav.jpg
541 ms
lapland-4-day-trips-nav.jpg
541 ms
lapland-5-day-trips-nav.jpg
578 ms
belmond-nav.jpg
577 ms
northern-belle-nav.jpg
577 ms
the-royal-scotsman-nav.jpg
602 ms
orient-express-venice-simplon-nav.jpg
601 ms
sandals-jamacia-holidays-nav.jpg
642 ms
sandals-bahamas-holidays-nav.jpg
653 ms
sandals-antigua-holidays-nav.jpg
653 ms
sandals-saint-lucia-holidays-nav.jpg
652 ms
disneyland-paris-600.jpg
677 ms
disney-world-florida-600.jpg
750 ms
disney-cruise-600.jpg
761 ms
sandals-holidays-600.jpg
803 ms
lapland-600.jpg
803 ms
belmond-600.jpg
878 ms
special-offers-disneyland-paris.jpg
752 ms
halloween-mickey.jpg
901 ms
hotels-disneyland-paris.jpg
827 ms
travelling-disneyland-paris.jpg
837 ms
family-holidays-disney-world-s.jpg
880 ms
disney-cruise-s.jpg
879 ms
lapland-s.jpg
904 ms
port-aventura-holidays-s.jpg
858 ms
lapland-1-day-trips-s.jpg
881 ms
lapland-3-day-trips-s.jpg
732 ms
modules.a4fd7e5489291affcf56.js
58 ms
lapland-4-day-trips-s.jpg
655 ms
lapland-5-day-trips-s.jpg
598 ms
belmond-s.jpg
591 ms
js
126 ms
northern-belle-s.jpg
499 ms
the-royal-scotsman-s.jpg
540 ms
fontawesome-webfont.woff
615 ms
orient-express-venice-simplon-s.jpg
500 ms
sandals-jamacia-holidays-s.jpg
519 ms
sandals-bahamas-holidays-s.jpg
521 ms
sandals-antigua-holidays-s.jpg
529 ms
sandals-saint-lucia-holidays-s.jpg
576 ms
atol-abta-travel-aware-ssl-secure.png
540 ms
instantbreaks.com accessibility score
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
[role] values are not valid
ARIA IDs are not unique
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Internationalization and localization
These are opportunities to improve the interpretation of your content by users in different locales.
Impact
Issue
<html> element does not have a [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
Image elements do not have [alt] attributes
Links do not have a discernible name
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
instantbreaks.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
Page has valid source maps
instantbreaks.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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
Document uses legible font sizes
EN
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Instantbreaks.com 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 Instantbreaks.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.
instantbreaks.com
Open Graph data is detected on the main page of Instantbreaks. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: