Tools & Wizards About Us
travelplanner.co.in screenshot

Report Summary

  • 12

    Performance

    Renders faster than
    25% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 67

    Best Practices

    More advanced features
    available than in
    24% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

travelplanner.co.in

Welcome to Travel Planner- we plan your travel, Tickets N Tours, Tickets N Tours in india, Tickets N Tours in Gujarat, Tickets N Tours in Vadodara, Ti...

Page Load Speed

7.5 sec in total

First Response

1.2 sec

Resources Loaded

6 sec

Page Rendered

340 ms

travelplanner.co.in screenshot

About Website

Visit travelplanner.co.in now to see the best up-to-date Travel Planner content and also check out these interesting facts you probably never knew about travelplanner.co.in

Founded in the year 2010, holidays packages, domestic and international Flight booking, airline booking, bus booking, hotel reservation, domestic and international taior maid tours, honeymoon packages...

Visit travelplanner.co.in

Key Findings

We analyzed Travelplanner.co.in page load time and found that the first response time was 1.2 sec and then it took 6.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 80% of websites can load faster.

Performance Metrics

travelplanner.co.in performance score

12

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.9 s

1/100

10%

LCP (Largest Contentful Paint)

Value29.2 s

0/100

25%

SI (Speed Index)

Value28.8 s

0/100

10%

TBT (Total Blocking Time)

Value960 ms

29/100

30%

CLS (Cumulative Layout Shift)

Value0.465

19/100

15%

TTI (Time to Interactive)

Value24.7 s

0/100

10%

Network Requests Diagram

travelplanner.co.in

1207 ms

js

95 ms

bootstrap.min.css

979 ms

font-awesome.min.css

605 ms

css

25 ms

Our browser made a total of 111 requests to load all elements on the main page. We found that 92% of them (102 requests) were addressed to the original Travelplanner.co.in, 3% (3 requests) were made to Fonts.gstatic.com and 1% (1 request) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Travelplanner.co.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 3.2 MB (66%)

Content Size

4.9 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Travelplanner.co.in main page is 4.9 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. 75% 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 3.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 129.2 kB

  • Original 152.4 kB
  • After minification 127.5 kB
  • After compression 23.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. This page needs HTML code to be minified as it can gain 24.9 kB, which is 16% of the original size. It is highly recommended that content of this web page should be compressed using GZIP, as it can save up to 129.2 kB or 85% of the original size.

Image Optimization

-61%

Potential reduce by 2.1 MB

  • Original 3.4 MB
  • After minification 1.3 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. Obviously, Travel Planner needs image optimization as it can save up to 2.1 MB or 61% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-69%

Potential reduce by 537.7 kB

  • Original 776.2 kB
  • After minification 747.3 kB
  • After compression 238.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 537.7 kB or 69% of the original size.

CSS Optimization

-86%

Potential reduce by 468.7 kB

  • Original 548.0 kB
  • After minification 515.0 kB
  • After compression 79.2 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. Travelplanner.co.in needs all CSS files to be minified and compressed as it can save up to 468.7 kB or 86% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (34%)

Requests Now

104

After Optimization

69

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

travelplanner.co.in

travelplanner.co.in

1207 ms

js

js

95 ms

bootstrap.min.css

bootstrap.min.css

979 ms

font-awesome.min.css

font-awesome.min.css

605 ms

css

css

25 ms

animate.min.css

animate.min.css

809 ms

settings.css

settings.css

655 ms

style.css

style.css

460 ms

jquery.bxslider.css

jquery.bxslider.css

464 ms

flexslider.css

flexslider.css

713 ms

style.css

style.css

1520 ms

custom.css

custom.css

799 ms

responsive.css

responsive.css

1131 ms

pace.min.js

pace.min.js

1029 ms

page-loading.js

page-loading.js

1019 ms

jquery-1.12.4.min.js

jquery-1.12.4.min.js

30 ms

api.js

api.js

43 ms

toastr.min.css

toastr.min.css

896 ms

jquery.form.js

jquery.form.js

980 ms

toastr.min.js

toastr.min.js

1036 ms

dwss.js

dwss.js

1036 ms

jquery.min.js

jquery.min.js

20 ms

bootstrap.min.js

bootstrap.min.js

48 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

1300 ms

jquery.noconflict.js

jquery.noconflict.js

1144 ms

modernizr.2.7.1.min.js

modernizr.2.7.1.min.js

1172 ms

jquery-migrate-1.2.1.min.js

jquery-migrate-1.2.1.min.js

1231 ms

jquery.placeholder.js

jquery.placeholder.js

1247 ms

jquery-ui.1.10.4.min.js

jquery-ui.1.10.4.min.js

1962 ms

bootstrap.min.js

bootstrap.min.js

1395 ms

jquery.themepunch.plugins.min.js

jquery.themepunch.plugins.min.js

1832 ms

jquery.themepunch.revolution.min.js

jquery.themepunch.revolution.min.js

1650 ms

jquery.bxslider.min.js

jquery.bxslider.min.js

1610 ms

jquery.flexslider.js

jquery.flexslider.js

1610 ms

jquery.stellar.min.js

jquery.stellar.min.js

1611 ms

waypoints.min.js

waypoints.min.js

1735 ms

theme-scripts.js

theme-scripts.js

1751 ms

scripts.js

scripts.js

1758 ms

logo2.png

logo2.png

518 ms

mobile-menu.png

mobile-menu.png

741 ms

travel_logo.png

travel_logo.png

742 ms

bg4.jpg

bg4.jpg

803 ms

grasss.png

grasss.png

1078 ms

suitcase.png

suitcase.png

921 ms

hotel.png

hotel.png

825 ms

fligts.png

fligts.png

829 ms

forex.png

forex.png

841 ms

cars.png

cars.png

1001 ms

cruses.png

cruses.png

1034 ms

eve.png

eve.png

1044 ms

cloud1.png

cloud1.png

1060 ms

cloud11.png

cloud11.png

1119 ms

sun.png

sun.png

1192 ms

bg3.jpg

bg3.jpg

1313 ms

badaal.png

badaal.png

1467 ms

area.png

area.png

1314 ms

girl1.png

girl1.png

1313 ms

11.png

11.png

1323 ms

arrow11.png

arrow11.png

1386 ms

22.png

22.png

1463 ms

33.png

33.png

1467 ms

44.png

44.png

1488 ms

arrow112.png

arrow112.png

1525 ms

66.png

66.png

1540 ms

S6uyw4BMUTPHjx4wWCWtFCc.woff

S6uyw4BMUTPHjx4wWCWtFCc.woff

38 ms

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

S6u9w4BMUTPHh7USSwiPHw3q5d0.woff

39 ms

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

S6u9w4BMUTPHh6UVSwiPHw3q5d0.woff

38 ms

NexaBlack.otf

NexaBlack.otf

1717 ms

soap-icons.woff

soap-icons.woff

1476 ms

77.png

77.png

1436 ms

slider.jpg

slider.jpg

1439 ms

baddal_new.png

baddal_new.png

1483 ms

pic1.png

pic1.png

1415 ms

pic2.png

pic2.png

1502 ms

pic3.png

pic3.png

1515 ms

center.png

center.png

1473 ms

pic4.png

pic4.png

1449 ms

pic5.png

pic5.png

1262 ms

pic6.png

pic6.png

1258 ms

fontawesome-webfont.woff

fontawesome-webfont.woff

1368 ms

pic7.png

pic7.png

1346 ms

pic8.png

pic8.png

1336 ms

slider_new.jpg

slider_new.jpg

1358 ms

girls3.png

girls3.png

1352 ms

rectangle.png

rectangle.png

1280 ms

travelo_process.png

travelo_process.png

1335 ms

5.jpg

5.jpg

1379 ms

6.jpg

6.jpg

1339 ms

3.jpg

3.jpg

1358 ms

4.jpg

4.jpg

1328 ms

1.jpg

1.jpg

1334 ms

2.jpg

2.jpg

1339 ms

3.jpg

3.jpg

1291 ms

4.jpg

4.jpg

1299 ms

1.png

1.png

1331 ms

2.png

2.png

1327 ms

logo11.png

logo11.png

1270 ms

w1.png

w1.png

1265 ms

dalia-logo.png

dalia-logo.png

1342 ms

icon-check.png

icon-check.png

1353 ms

process-background.jpg

process-background.jpg

1376 ms

hover-effect.png

hover-effect.png

1332 ms

process-background-1.jpg

process-background-1.jpg

1288 ms

process-background-2.jpg

process-background-2.jpg

1239 ms

sky.png

sky.png

1330 ms

holiday_ballon.png

holiday_ballon.png

1269 ms

island.png

island.png

1302 ms

blank.png

blank.png

1317 ms

timer.png

timer.png

1284 ms

bg_4-11.png

bg_4-11.png

1200 ms

skin1-logo.png

skin1-logo.png

221 ms

Accessibility Review

travelplanner.co.in accessibility score

77

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

[id] attributes on active, focusable elements are not unique

High

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

High

<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

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Best Practices

travelplanner.co.in best practices score

67

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

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Page has valid source maps

SEO Factors

travelplanner.co.in SEO score

77

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

High

Image elements do not have [alt] attributes

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

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 Travelplanner.co.in 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 Travelplanner.co.in 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

travelplanner.co.in

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