Tools & Wizards About Us
hortensetravel.com screenshot

Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 91

    Accessibility

    Visual factors better than
    that of 76% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 92

    SEO

    Google-friendlier than
    74% of websites

hortensetravel.com

Travel Guide For Portugal | Tourist Attractions In Portugal | Hortense Travel Guide And Itineraries

Page Load Speed

12.3 sec in total

First Response

86 ms

Resources Loaded

11.7 sec

Page Rendered

489 ms

hortensetravel.com screenshot

About Website

Click here to check amazing Hortense Travel content. Otherwise, check out these important facts you probably never knew about hortensetravel.com

At Hortense Travel we have the finest of travel advisors that curate itineraries for cities like Lisbon, Porto, Douro and much more, jam-packed with places to visit and the most touristy things to do ...

Visit hortensetravel.com

Key Findings

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

Performance Metrics

hortensetravel.com performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.0 s

4/100

10%

LCP (Largest Contentful Paint)

Value16.7 s

0/100

25%

SI (Speed Index)

Value15.9 s

0/100

10%

TBT (Total Blocking Time)

Value2,330 ms

5/100

30%

CLS (Cumulative Layout Shift)

Value0.066

97/100

15%

TTI (Time to Interactive)

Value32.8 s

0/100

10%

Network Requests Diagram

hortensetravel.com

86 ms

hortensetravel.com

2372 ms

sbi-styles.min.css

202 ms

style.min.css

59 ms

mediaelementplayer-legacy.min.css

64 ms

Our browser made a total of 155 requests to load all elements on the main page. We found that 72% of them (111 requests) were addressed to the original Hortensetravel.com, 23% (36 requests) were made to C0.wp.com and 1% (2 requests) were made to Stats.wp.com. The less responsive or slowest element that took the longest time to load (5.9 sec) belongs to the original domain Hortensetravel.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 727.1 kB (11%)

Content Size

6.5 MB

After Optimization

5.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Hortensetravel.com main page is 6.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. 80% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 5.1 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 134.5 kB

  • Original 162.4 kB
  • After minification 162.3 kB
  • After compression 27.9 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 134.5 kB or 83% of the original size.

Image Optimization

-8%

Potential reduce by 399.4 kB

  • Original 5.1 MB
  • After minification 4.7 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. Hortense Travel images are well optimized though.

JavaScript Optimization

-14%

Potential reduce by 114.8 kB

  • Original 816.2 kB
  • After minification 816.2 kB
  • After compression 701.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 114.8 kB or 14% of the original size.

CSS Optimization

-20%

Potential reduce by 78.4 kB

  • Original 397.5 kB
  • After minification 397.4 kB
  • After compression 319.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. Hortensetravel.com needs all CSS files to be minified and compressed as it can save up to 78.4 kB or 20% of the original size.

Requests Breakdown

Number of requests can be reduced by 118 (83%)

Requests Now

142

After Optimization

24

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

hortensetravel.com

hortensetravel.com

86 ms

hortensetravel.com

hortensetravel.com

2372 ms

sbi-styles.min.css

sbi-styles.min.css

202 ms

style.min.css

style.min.css

59 ms

mediaelementplayer-legacy.min.css

mediaelementplayer-legacy.min.css

64 ms

wp-mediaelement.min.css

wp-mediaelement.min.css

66 ms

wc-blocks-vendors-style.css

wc-blocks-vendors-style.css

66 ms

wc-blocks-style.css

wc-blocks-style.css

67 ms

style.min.css

style.min.css

75 ms

style.min.css

style.min.css

74 ms

style.min.css

style.min.css

79 ms

style.min.css

style.min.css

81 ms

style.min.css

style.min.css

81 ms

style.min.css

style.min.css

88 ms

aalb_basics.css

aalb_basics.css

259 ms

styles.css

styles.css

422 ms

style.css

style.css

259 ms

rs6.css

rs6.css

292 ms

wordpress-svg-icon-plugin-style.min.css

wordpress-svg-icon-plugin-style.min.css

295 ms

frontend.css

frontend.css

435 ms

wpmenucart-icons.min.css

wpmenucart-icons.min.css

471 ms

wpmenucart-main.min.css

wpmenucart-main.min.css

501 ms

testimonial-rotator-style.css

testimonial-rotator-style.css

500 ms

font-awesome.min.css

font-awesome.min.css

505 ms

modules.min.css

modules.min.css

671 ms

dripicons.css

dripicons.css

741 ms

style.min.css

style.min.css

740 ms

fontawesome-all.min.css

fontawesome-all.min.css

737 ms

ionicons.min.css

ionicons.min.css

832 ms

style.css

style.css

864 ms

style.css

style.css

903 ms

simple-line-icons.css

simple-line-icons.css

938 ms

woocommerce.min.css

woocommerce.min.css

970 ms

woocommerce-responsive.min.css

woocommerce-responsive.min.css

975 ms

style_dynamic.css

style_dynamic.css

1061 ms

modules-responsive.min.css

modules-responsive.min.css

1064 ms

style_dynamic_responsive.css

style_dynamic_responsive.css

1151 ms

js_composer.min.css

js_composer.min.css

1137 ms

ytprefs.min.css

ytprefs.min.css

1172 ms

select2.css

select2.css

77 ms

jetpack.css

jetpack.css

77 ms

jquery.min.js

jquery.min.js

84 ms

jquery-migrate.min.js

jquery-migrate.min.js

84 ms

revolution.tools.min.js

revolution.tools.min.js

1061 ms

rs6.min.js

rs6.min.js

1317 ms

imagesloaded.min.js

imagesloaded.min.js

83 ms

masonry.min.js

masonry.min.js

84 ms

jquery.masonry.min.js

jquery.masonry.min.js

84 ms

general.min.js

general.min.js

1299 ms

wpmenucart-ajax-assist.min.js

wpmenucart-ajax-assist.min.js

1301 ms

jquery.blockUI.min.js

jquery.blockUI.min.js

83 ms

add-to-cart.min.js

add-to-cart.min.js

84 ms

cart.js

cart.js

1370 ms

woocommerce-add-to-cart.js

woocommerce-add-to-cart.js

1373 ms

jquery.cycletwo.js

jquery.cycletwo.js

1247 ms

s-202437.js

s-202437.js

80 ms

js

js

101 ms

js.cookie.min.js

js.cookie.min.js

82 ms

woocommerce.min.js

woocommerce.min.js

82 ms

core.min.js

core.min.js

83 ms

tabs.min.js

tabs.min.js

84 ms

accordion.min.js

accordion.min.js

83 ms

mediaelement-and-player.min.js

mediaelement-and-player.min.js

84 ms

mediaelement-migrate.min.js

mediaelement-migrate.min.js

84 ms

wp-mediaelement.min.js

wp-mediaelement.min.js

83 ms

underscore.min.js

underscore.min.js

85 ms

select2.full.min.js

select2.full.min.js

84 ms

e-202437.js

e-202437.js

76 ms

selectWoo.full.min.js

selectWoo.full.min.js

84 ms

wp-polyfill-inert.min.js

wp-polyfill-inert.min.js

85 ms

regenerator-runtime.min.js

regenerator-runtime.min.js

85 ms

wp-polyfill.min.js

wp-polyfill.min.js

85 ms

react.min.js

react.min.js

85 ms

react-dom.min.js

react-dom.min.js

85 ms

common-vendors.css

common-vendors.css

1483 ms

common.css

common.css

1339 ms

feed.css

feed.css

1242 ms

front-app.css

front-app.css

1262 ms

jquery.cycletwo.addons.js

jquery.cycletwo.addons.js

1286 ms

ytprefs.min.js

ytprefs.min.js

1327 ms

index.js

index.js

1307 ms

index.js

index.js

1292 ms

idle-timer.min.js

idle-timer.min.js

1320 ms

custom.js

custom.js

1297 ms

frontend.min.js

frontend.min.js

1328 ms

jquery.appear.js

jquery.appear.js

1324 ms

modernizr.min.js

modernizr.min.js

1265 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

1360 ms

jquery.plugin.js

jquery.plugin.js

1317 ms

owl.carousel.min.js

owl.carousel.min.js

1297 ms

jquery.waypoints.min.js

jquery.waypoints.min.js

1313 ms

fluidvids.min.js

fluidvids.min.js

1327 ms

perfect-scrollbar.jquery.min.js

perfect-scrollbar.jquery.min.js

1290 ms

ScrollToPlugin.min.js

ScrollToPlugin.min.js

1231 ms

parallax.min.js

parallax.min.js

1230 ms

jquery.waitforimages.js

jquery.waitforimages.js

1332 ms

jquery.prettyPhoto.js

jquery.prettyPhoto.js

1156 ms

jquery.easing.1.3.js

jquery.easing.1.3.js

1328 ms

isotope.pkgd.min.js

isotope.pkgd.min.js

1270 ms

packery-mode.pkgd.min.js

packery-mode.pkgd.min.js

1263 ms

swiper.min.js

swiper.min.js

1263 ms

jquery-ui.min.js

jquery-ui.min.js

1234 ms

jquery.ui.touch-punch.min.js

jquery.ui.touch-punch.min.js

1377 ms

jquery.countdown.min.js

jquery.countdown.min.js

1280 ms

counter.js

counter.js

1147 ms

absoluteCounter.min.js

absoluteCounter.min.js

1233 ms

typed.js

typed.js

1251 ms

jquery.fullPage.min.js

jquery.fullPage.min.js

1289 ms

easypiechart.js

easypiechart.js

1226 ms

curtain.js

curtain.js

1350 ms

jquery.multiscroll.min.js

jquery.multiscroll.min.js

1282 ms

modules.min.js

modules.min.js

1231 ms

frontend.min.js

frontend.min.js

1232 ms

new-tab.js

new-tab.js

1265 ms

fitvids.min.js

fitvids.min.js

1234 ms

NEW-HORTENSE-LOGO.png

NEW-HORTENSE-LOGO.png

384 ms

NEW-HORTENSE-LOGO-3.png

NEW-HORTENSE-LOGO-3.png

507 ms

h1-backround-1.jpg

h1-backround-1.jpg

118 ms

js_composer_front.min.js

js_composer_front.min.js

1295 ms

xfbml.customerchat.js

xfbml.customerchat.js

74 ms

runtime.js

runtime.js

1235 ms

common-vendors.js

common-vendors.js

1229 ms

h1-backround-1.jpg

h1-backround-1.jpg

76 ms

common.js

common.js

1074 ms

feed.js

feed.js

1241 ms

47 ms

front-app.js

front-app.js

1193 ms

fa-brands-400.woff

fa-brands-400.woff

1248 ms

ElegantIcons.woff

ElegantIcons.woff

1326 ms

NEW-HORTENSE-LOGO.png

NEW-HORTENSE-LOGO.png

1183 ms

epicRide.ttf

epicRide.ttf

1240 ms

fa-solid-900.woff

fa-solid-900.woff

1220 ms

fa-regular-400.woff

fa-regular-400.woff

1254 ms

ETmonarch_2.ttf

ETmonarch_2.ttf

1241 ms

sbi-sprite.png

sbi-sprite.png

1332 ms

11.-View-from-Sao-Pedro-De-Alcantara-Viewpoint.jpg

11.-View-from-Sao-Pedro-De-Alcantara-Viewpoint.jpg

1315 ms

IMG_0628.jpg

IMG_0628.jpg

1373 ms

3-650x800.png

3-650x800.png

1387 ms

NEW-HORTENSE-LOGO-3.png

NEW-HORTENSE-LOGO-3.png

1363 ms

6-650x800.png

6-650x800.png

1264 ms

4-650x800.png

4-650x800.png

1319 ms

2-650x800.png

2-650x800.png

1316 ms

1.0-week-Portugal-south-650x800.png

1.0-week-Portugal-south-650x800.png

1431 ms

5-650x800.png

5-650x800.png

1315 ms

luxury-hotels-lisbon-4.jpg

luxury-hotels-lisbon-4.jpg

1205 ms

28-lombok-guide.jpg

28-lombok-guide.jpg

1287 ms

20-top-5-islands-near-bali.jpg

20-top-5-islands-near-bali.jpg

1299 ms

timeline.svg

timeline.svg

1310 ms

timeline-pin.png

timeline-pin.png

1293 ms

hortensetravel.com

hortensetravel.com

4169 ms

admin-ajax.php

admin-ajax.php

4378 ms

admin-ajax.php

admin-ajax.php

5806 ms

ionicons.ttf

ionicons.ttf

5627 ms

dripicons-v2.woff

dripicons-v2.woff

5879 ms

29 ms

Accessibility Review

hortensetravel.com accessibility score

91

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.

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

<frame> or <iframe> elements do not have a title

High

Links do not have a discernible name

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

hortensetravel.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

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

hortensetravel.com SEO score

92

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

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 Hortensetravel.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 Hortensetravel.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

hortensetravel.com

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