Tools & Wizards About Us
travelwithjan.com screenshot

Report Summary

  • 17

    Performance

    Renders faster than
    32% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 71

    SEO

    Google-friendlier than
    30% of websites

travelwithjan.com

Travel With Jan

Page Load Speed

54.1 sec in total

First Response

9.1 sec

Resources Loaded

42.5 sec

Page Rendered

2.5 sec

travelwithjan.com screenshot

About Website

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

Visit travelwithjan.com

Key Findings

We analyzed Travelwithjan.com page load time and found that the first response time was 9.1 sec and then it took 45 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there were 36 request timeouts, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

travelwithjan.com performance score

17

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value9.1 s

0/100

10%

LCP (Largest Contentful Paint)

Value22.1 s

0/100

25%

SI (Speed Index)

Value20.7 s

0/100

10%

TBT (Total Blocking Time)

Value1,570 ms

13/100

30%

CLS (Cumulative Layout Shift)

Value0.097

90/100

15%

TTI (Time to Interactive)

Value29.0 s

0/100

10%

Network Requests Diagram

travelwithjan.com

9051 ms

system.base.css

20091 ms

system.menus.css

20090 ms

system.messages.css

20091 ms

system.theme.css

20090 ms

Our browser made a total of 75 requests to load all elements on the main page. We found that 60% of them (45 requests) were addressed to the original Travelwithjan.com, 16% (12 requests) were made to Feedjit.com and 7% (5 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (20.1 sec) belongs to the original domain Travelwithjan.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 514.5 kB (50%)

Content Size

1.0 MB

After Optimization

520.3 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-82%

Potential reduce by 77.0 kB

  • Original 93.4 kB
  • After minification 90.1 kB
  • After compression 16.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 77.0 kB or 82% of the original size.

Image Optimization

-5%

Potential reduce by 17.3 kB

  • Original 334.5 kB
  • After minification 317.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. Travel With Jan images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 368.9 kB

  • Original 541.5 kB
  • After minification 482.7 kB
  • After compression 172.6 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 368.9 kB or 68% of the original size.

CSS Optimization

-79%

Potential reduce by 51.3 kB

  • Original 65.3 kB
  • After minification 47.9 kB
  • After compression 14.0 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. Travelwithjan.com needs all CSS files to be minified and compressed as it can save up to 51.3 kB or 79% of the original size.

Requests Breakdown

Number of requests can be reduced by 20 (54%)

Requests Now

37

After Optimization

17

  • AJAX
  • Images
  • JavaScript
  • CSS

The browser has sent 37 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Travel With Jan. 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.

Network Requests Diagram

travelwithjan.com

travelwithjan.com

9051 ms

system.base.css

system.base.css

20091 ms

system.menus.css

system.menus.css

20090 ms

system.messages.css

system.messages.css

20091 ms

system.theme.css

system.theme.css

20090 ms

comment.css

comment.css

20087 ms

field.css

field.css

20086 ms

mollom.css

mollom.css

20087 ms

node.css

node.css

20086 ms

search.css

search.css

20085 ms

user.css

user.css

20086 ms

views.css

views.css

20078 ms

ckeditor.css

ckeditor.css

20077 ms

ctools.css

ctools.css

20077 ms

panels.css

panels.css

20075 ms

gmap.css

gmap.css

20074 ms

style.css

style.css

20071 ms

media.css

media.css

20070 ms

jquery.js

jquery.js

20068 ms

jquery.once.js

jquery.once.js

20068 ms

drupal.js

drupal.js

20066 ms

jquery.cookie.js

jquery.cookie.js

20065 ms

jquery.form.js

jquery.form.js

20065 ms

ajax.js

ajax.js

20062 ms

admin_devel.js

admin_devel.js

20058 ms

newsletter.js

newsletter.js

20057 ms

infobubble.js

infobubble.js

20060 ms

progress.js

progress.js

20060 ms

infobubble_extended.js

infobubble_extended.js

20060 ms

gmap.js

gmap.js

20056 ms

js

js

123 ms

icon.js

icon.js

20100 ms

marker.js

marker.js

20100 ms

highlight.js

highlight.js

20099 ms

poly.js

poly.js

20100 ms

gmap_markers.js

gmap_markers.js

495 ms

markerloader_static.js

markerloader_static.js

20094 ms

gmap_marker.js

gmap_marker.js

20093 ms

custom.js

custom.js

20094 ms

282 ms

addthis.js

addthis.js

581 ms

IMG_0052.JPG

IMG_0052.JPG

8628 ms

sm-share-en.gif

sm-share-en.gif

110 ms

IMG_0003.JPG

IMG_0003.JPG

2203 ms

_MG_0030.JPG

_MG_0030.JPG

5175 ms

IMG_0012.JPG

IMG_0012.JPG

5278 ms

IMG_0173.JPG

IMG_0173.JPG

13558 ms

sdk.js

sdk.js

367 ms

like.php

like.php

306 ms

like.php

like.php

549 ms

like.php

like.php

705 ms

like.php

like.php

682 ms

inj_tf.css

inj_tf.css

217 ms

travelwithjan.com

travelwithjan.com

2 ms

228 ms

464 ms

Sh_BYjerrZ8.js

Sh_BYjerrZ8.js

998 ms

LVx-xkvaJ0b.png

LVx-xkvaJ0b.png

1116 ms

115 ms

xd_arbiter.php

xd_arbiter.php

374 ms

xd_arbiter.php

xd_arbiter.php

738 ms

b1_D09100_2853A8.png

b1_D09100_2853A8.png

160 ms

tf.html

tf.html

157 ms

overlay.png

overlay.png

144 ms

overlay2.png

overlay2.png

143 ms

us.png

us.png

144 ms

th.png

th.png

1436 ms

bb.png

bb.png

291 ms

in.png

in.png

290 ms

dc.js

dc.js

190 ms

__utm.gif

__utm.gif

54 ms

common.js

common.js

26 ms

util.js

util.js

70 ms

stats.js

stats.js

69 ms

AuthenticationService.Authenticate

AuthenticationService.Authenticate

272 ms

Accessibility Review

travelwithjan.com accessibility score

83

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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 [lang] attribute

Best Practices

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

SEO Factors

travelwithjan.com SEO score

71

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

High

Tap targets are not sized appropriately

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

travelwithjan.com

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