Tools & Wizards About Us
traffline.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

traffline.com

Ridlr - Real Time Traffic Alerts |Local Timetable | Traffic Updates in Delhi, Mumbai

Page Load Speed

5.5 sec in total

First Response

451 ms

Resources Loaded

4.5 sec

Page Rendered

494 ms

traffline.com screenshot

About Website

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

Ridlr is India's Premier Public Transport App that finds the best routes for your daily communtes and lets you travel smarter and cashless on public transport.

Visit traffline.com

Key Findings

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

Performance Metrics

traffline.com performance score

0

Network Requests Diagram

traffline.com

451 ms

ridlr.in

742 ms

jquery-all.css

431 ms

style.css

679 ms

easydropdown.css

438 ms

Our browser made a total of 128 requests to load all elements on the main page. We found that 1% of them (1 request) were addressed to the original Traffline.com, 41% (52 requests) were made to Ridlr.in and 40% (51 requests) were made to Maps.googleapis.com. The less responsive or slowest element that took the longest time to load (2.6 sec) relates to the external source Ridlr.in.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.3 MB (43%)

Content Size

3.0 MB

After Optimization

1.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Traffline.com main page is 3.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. 70% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.

HTML Optimization

-85%

Potential reduce by 77.5 kB

  • Original 90.9 kB
  • After minification 78.5 kB
  • After compression 13.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. This page needs HTML code to be minified as it can gain 12.4 kB, which is 14% 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 77.5 kB or 85% of the original size.

Image Optimization

-5%

Potential reduce by 63.3 kB

  • Original 1.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. Traffline images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 648.7 kB

  • Original 948.7 kB
  • After minification 881.2 kB
  • After compression 300.0 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 648.7 kB or 68% of the original size.

CSS Optimization

-83%

Potential reduce by 515.9 kB

  • Original 625.0 kB
  • After minification 585.4 kB
  • After compression 109.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. Traffline.com needs all CSS files to be minified and compressed as it can save up to 515.9 kB or 83% of the original size.

Requests Breakdown

Number of requests can be reduced by 57 (48%)

Requests Now

119

After Optimization

62

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

traffline.com

traffline.com

451 ms

ridlr.in

ridlr.in

742 ms

jquery-all.css

jquery-all.css

431 ms

style.css

style.css

679 ms

easydropdown.css

easydropdown.css

438 ms

jquery-all.js

jquery-all.js

691 ms

style_ridlr.css

style_ridlr.css

443 ms

bootstrap.min.css

bootstrap.min.css

35 ms

style_ridlr.css

style_ridlr.css

441 ms

style_new.css

style_new.css

647 ms

move-top.js

move-top.js

652 ms

easing.js

easing.js

656 ms

main.js

main.js

657 ms

owl.carousel.css

owl.carousel.css

863 ms

owl.theme.css

owl.theme.css

869 ms

owl.carousel.js

owl.carousel.js

875 ms

cycle.js

cycle.js

883 ms

app.js

app.js

896 ms

mmi_polys_version_2.3.js

mmi_polys_version_2.3.js

895 ms

index.js

index.js

1096 ms

inline.js

inline.js

1094 ms

inclusion_v2.3.js

inclusion_v2.3.js

1102 ms

logo_small.png

logo_small.png

1100 ms

loader1.gif

loader1.gif

1327 ms

phone_new.png

phone_new.png

1363 ms

border.png

border.png

1314 ms

video.png

video.png

2614 ms

missed_call_white.png

missed_call_white.png

1322 ms

AppDownloadbutton.png

AppDownloadbutton.png

1321 ms

css

css

25 ms

analytics.js

analytics.js

42 ms

7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf

7XUFZ5tgS-tD6QamInJTcU3KvHLhcNjEHFQzwNtdMQY.ttf

41 ms

anMUvcNT0H1YN4FII8wpr4e2tK5W43RXgBRKkM4A5Qg.ttf

anMUvcNT0H1YN4FII8wpr4e2tK5W43RXgBRKkM4A5Qg.ttf

42 ms

collect

collect

14 ms

collect

collect

57 ms

sprite_icons_header_24px_ridlr.png

sprite_icons_header_24px_ridlr.png

656 ms

sprite_icons_navigations_48px_v1.png

sprite_icons_navigations_48px_v1.png

659 ms

arrow_white_down.png

arrow_white_down.png

647 ms

arrow_white_up.png

arrow_white_up.png

652 ms

sprite_icons_header_24px.png

sprite_icons_header_24px.png

692 ms

iAoONhwiVNo

iAoONhwiVNo

85 ms

bnr.jpg

bnr.jpg

1497 ms

welcome-sprit.png

welcome-sprit.png

1066 ms

features-banner.jpg

features-banner.jpg

1285 ms

features-sprit.png

features-sprit.png

855 ms

app-banner.jpg

app-banner.jpg

895 ms

r_mobile-2.png

r_mobile-2.png

1073 ms

download-banner.jpg

download-banner.jpg

1113 ms

download-sprit.png

download-sprit.png

1333 ms

getin-sprit.png

getin-sprit.png

1290 ms

footer-sprit_1.png

footer-sprit_1.png

1330 ms

cd-top-arrow.svg

cd-top-arrow.svg

1500 ms

www-embed-player-vflfNyN_r.css

www-embed-player-vflfNyN_r.css

28 ms

www-embed-player.js

www-embed-player.js

51 ms

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

Tqng9ngJVK4Gqvh3e602hP-HqlN49KFEUSDtmrOPmWo.js

96 ms

ad_status.js

ad_status.js

96 ms

zN7GBFwfMP4uA6AR0HCoLQ.ttf

zN7GBFwfMP4uA6AR0HCoLQ.ttf

94 ms

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf

127 ms

pagenate.png

pagenate.png

1305 ms

arrow-2.png

arrow-2.png

1299 ms

arrow-1.png

arrow-1.png

1300 ms

1.png

1.png

1462 ms

2.png

2.png

1727 ms

3.png

3.png

1521 ms

AjaxLoader.gif

AjaxLoader.gif

1555 ms

tapstream.js

tapstream.js

75 ms

js

js

43 ms

common.js

common.js

13 ms

map.js

map.js

38 ms

util.js

util.js

95 ms

marker.js

marker.js

95 ms

infowindow5_1.js

infowindow5_1.js

281 ms

.gif

.gif

87 ms

onion.js

onion.js

34 ms

openhand_8_8.cur

openhand_8_8.cur

105 ms

ViewportInfoService.GetViewportInfo

ViewportInfoService.GetViewportInfo

83 ms

stats.js

stats.js

62 ms

controls.js

controls.js

61 ms

transparent.png

transparent.png

51 ms

css

css

116 ms

google4.png

google4.png

64 ms

marker_current1.png

marker_current1.png

231 ms

mapcnt6.png

mapcnt6.png

68 ms

sv5.png

sv5.png

123 ms

vt

vt

114 ms

vt

vt

97 ms

vt

vt

94 ms

vt

vt

71 ms

vt

vt

109 ms

vt

vt

112 ms

vt

vt

110 ms

vt

vt

109 ms

vt

vt

108 ms

vt

vt

147 ms

vt

vt

145 ms

vt

vt

113 ms

vt

vt

150 ms

vt

vt

112 ms

vt

vt

113 ms

vt

vt

141 ms

vt

vt

141 ms

vt

vt

143 ms

vt

vt

145 ms

vt

vt

146 ms

vt

vt

147 ms

vt

vt

148 ms

vt

vt

149 ms

vt

vt

151 ms

vt

vt

155 ms

vt

vt

151 ms

vt

vt

158 ms

vt

vt

153 ms

vt

vt

155 ms

vt

vt

158 ms

vt

vt

165 ms

vt

vt

159 ms

vt

vt

164 ms

vt

vt

166 ms

vt

vt

168 ms

vt

vt

166 ms

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

Hgo13k-tfSpn0qi1SFdUfaCWcynf_cDxXwCLxiixG1c.ttf

19 ms

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

d-6IYplOFocCacKzxwXSOKCWcynf_cDxXwCLxiixG1c.ttf

50 ms

vt

vt

113 ms

vt

vt

113 ms

vt

vt

120 ms

vt

vt

112 ms

vt

vt

80 ms

vt

vt

93 ms

SEO Factors

traffline.com SEO score

0

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

traffline.com

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