Tools & Wizards About Us
travelpeppy.com screenshot

Report Summary

  • 37

    Performance

    Renders faster than
    57% of other websites

  • 83

    Accessibility

    Visual factors better than
    that of 56% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 90

    SEO

    Google-friendlier than
    68% of websites

travelpeppy.com

Travelpeppy : Travel Blog for beautiful destinations | Travelpeppy

Page Load Speed

6 sec in total

First Response

2.1 sec

Resources Loaded

3 sec

Page Rendered

873 ms

travelpeppy.com screenshot

About Website

Visit travelpeppy.com now to see the best up-to-date Travelpeppy content for India and also check out these interesting facts you probably never knew about travelpeppy.com

Travelpeppy is a travel blog covering beautiful destinations from around the world. Get free coupons and travel deals for your vacation.

Visit travelpeppy.com

Key Findings

We analyzed Travelpeppy.com page load time and found that the first response time was 2.1 sec and then it took 3.9 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

travelpeppy.com performance score

37

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.6 s

33/100

10%

LCP (Largest Contentful Paint)

Value8.4 s

2/100

25%

SI (Speed Index)

Value6.1 s

45/100

10%

TBT (Total Blocking Time)

Value300 ms

78/100

30%

CLS (Cumulative Layout Shift)

Value0.519

15/100

15%

TTI (Time to Interactive)

Value9.4 s

30/100

10%

Network Requests Diagram

travelpeppy.com

2079 ms

wp-emoji-release.min.js

15 ms

style.min.css

17 ms

wpp.css

21 ms

virtue.css

46 ms

Our browser made a total of 33 requests to load all elements on the main page. We found that 70% of them (23 requests) were addressed to the original Travelpeppy.com, 9% (3 requests) were made to Fonts.gstatic.com and 6% (2 requests) were made to Platform-api.sharethis.com. The less responsive or slowest element that took the longest time to load (2.1 sec) belongs to the original domain Travelpeppy.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 117.4 kB (28%)

Content Size

412.9 kB

After Optimization

295.5 kB

  • HTML
  • Images
  • JavaScript
  • CSS

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

HTML Optimization

-85%

Potential reduce by 84.5 kB

  • Original 99.7 kB
  • After minification 88.8 kB
  • After compression 15.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 10.8 kB, which is 11% 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 84.5 kB or 85% of the original size.

Image Optimization

-0%

Potential reduce by 0 B

  • Original 79.6 kB
  • After minification 79.6 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. Travelpeppy images are well optimized though.

JavaScript Optimization

-18%

Potential reduce by 32.2 kB

  • Original 183.7 kB
  • After minification 183.7 kB
  • After compression 151.5 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 32.2 kB or 18% of the original size.

CSS Optimization

-1%

Potential reduce by 743 B

  • Original 50.0 kB
  • After minification 49.7 kB
  • After compression 49.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. Travelpeppy.com has all CSS files already compressed.

Requests Breakdown

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

Requests Now

27

After Optimization

7

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

travelpeppy.com

travelpeppy.com

2079 ms

wp-emoji-release.min.js

wp-emoji-release.min.js

15 ms

style.min.css

style.min.css

17 ms

wpp.css

wpp.css

21 ms

virtue.css

virtue.css

46 ms

default.css

default.css

38 ms

css

css

68 ms

wpp.min.js

wpp.min.js

72 ms

sharethis.js

sharethis.js

75 ms

jquery.min.js

jquery.min.js

81 ms

jquery-migrate.min.js

jquery-migrate.min.js

77 ms

adsbygoogle.js

adsbygoogle.js

103 ms

smush-lazy-load.min.js

smush-lazy-load.min.js

74 ms

bootstrap-min.js

bootstrap-min.js

86 ms

hoverIntent.min.js

hoverIntent.min.js

73 ms

imagesloaded.min.js

imagesloaded.min.js

73 ms

masonry.min.js

masonry.min.js

88 ms

plugins-min.js

plugins-min.js

87 ms

magnific.js

magnific.js

87 ms

virtue-lightbox-init-min.js

virtue-lightbox-init-min.js

88 ms

main-min.js

main-min.js

92 ms

sharethis.js

sharethis.js

32 ms

analytics.js

analytics.js

278 ms

loader.gif

loader.gif

206 ms

show_ads_impl.js

show_ads_impl.js

221 ms

zrt_lookup.html

zrt_lookup.html

215 ms

S6uyw4BMUTPHjx4wWw.ttf

S6uyw4BMUTPHjx4wWw.ttf

169 ms

S6u9w4BMUTPHh6UVSwiPHA.ttf

S6u9w4BMUTPHh6UVSwiPHA.ttf

177 ms

S6u9w4BMUTPHh50XSwiPHA.ttf

S6u9w4BMUTPHh50XSwiPHA.ttf

179 ms

kt-font-awesome.ttf

kt-font-awesome.ttf

166 ms

Capri-by-Fraser-Singapore-travelpeppy.jpg

Capri-by-Fraser-Singapore-travelpeppy.jpg

82 ms

slide_direction.png

slide_direction.png

170 ms

Travelpeppy-logo.jpg

Travelpeppy-logo.jpg

171 ms

Accessibility Review

travelpeppy.com accessibility score

83

Accessibility Issues

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

High

[aria-hidden="true"] elements contain focusable descendents

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

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

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

travelpeppy.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

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

travelpeppy.com SEO score

90

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

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

travelpeppy.com

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