Tools & Wizards About Us
5thavefloral.rtrk.com screenshot

Report Summary

  • 0

    Performance

  • 0

    Accessibility

  • 0

    Best Practices

  • 0

    SEO

5thavefloral.rtrk.com

Seize your potential | LocaliQ

Page Load Speed

4.3 sec in total

First Response

243 ms

Resources Loaded

3.7 sec

Page Rendered

280 ms

5thavefloral.rtrk.com screenshot

About Website

Click here to check amazing 5 Thavefloral Rtrk content for United States. Otherwise, check out these important facts you probably never knew about 5thavefloral.rtrk.com

LocaliQ is a marketing platform that helps businesses find, convert, and keep customers with a suite of marketing products.

Visit 5thavefloral.rtrk.com

Key Findings

We analyzed 5thavefloral.rtrk.com page load time and found that the first response time was 243 ms and then it took 4 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

5thavefloral.rtrk.com performance score

0

Network Requests Diagram

5thavefloral.rtrk.com

243 ms

index5.html

73 ms

5thavefloral-px.rtrk.com

262 ms

coupon.css

273 ms

rl.js

373 ms

Our browser made a total of 100 requests to load all elements on the main page. We found that 2% of them (2 requests) were addressed to the original 5thavefloral.rtrk.com, 50% (50 requests) were made to Folimg.com and 25% (25 requests) were made to Urlwww--folimg--com.rtrk.com. The less responsive or slowest element that took the longest time to load (1.4 sec) relates to the external source Urlwww--folimg--com.rtrk.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 276.6 kB (58%)

Content Size

480.4 kB

After Optimization

203.8 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of 5thavefloral.rtrk.com main page is 480.4 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. 35% of websites need less resources to load. Javascripts take 362.6 kB which makes up the majority of the site volume.

HTML Optimization

-62%

Potential reduce by 1.6 kB

  • Original 2.5 kB
  • After minification 2.4 kB
  • After compression 974 B

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 1.6 kB or 62% of the original size.

Image Optimization

-0%

Potential reduce by 128 B

  • Original 81.5 kB
  • After minification 81.4 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. 5 Thavefloral Rtrk images are well optimized though.

JavaScript Optimization

-69%

Potential reduce by 249.1 kB

  • Original 362.6 kB
  • After minification 357.5 kB
  • After compression 113.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 249.1 kB or 69% of the original size.

CSS Optimization

-76%

Potential reduce by 25.8 kB

  • Original 33.7 kB
  • After minification 29.0 kB
  • After compression 7.9 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. 5thavefloral.rtrk.com needs all CSS files to be minified and compressed as it can save up to 25.8 kB or 76% of the original size.

Requests Breakdown

Number of requests can be reduced by 67 (71%)

Requests Now

95

After Optimization

28

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

5thavefloral.rtrk.com

5thavefloral.rtrk.com

243 ms

index5.html

index5.html

73 ms

5thavefloral-px.rtrk.com

5thavefloral-px.rtrk.com

262 ms

coupon.css

coupon.css

273 ms

rl.js

rl.js

373 ms

5thavefloral-px.rtrk.com

5thavefloral-px.rtrk.com

713 ms

coupon.css

coupon.css

129 ms

javascript.jscript

javascript.jscript

112 ms

prototype.js

prototype.js

411 ms

effects.js

effects.js

402 ms

lib.js

lib.js

373 ms

opt_in.js

opt_in.js

255 ms

inner.css

inner.css

482 ms

common.css

common.css

284 ms

default.css

default.css

930 ms

satelliteLib-0acc6bba87ae1dc9bdcc742d5cc46ad0c1bd1152.js

satelliteLib-0acc6bba87ae1dc9bdcc742d5cc46ad0c1bd1152.js

8 ms

TrackLandingPage_src.js

TrackLandingPage_src.js

196 ms

satellite-52fbad1899943605b60000f6.js

satellite-52fbad1899943605b60000f6.js

5 ms

bg-spring.jpg

bg-spring.jpg

47 ms

39-6226AA.gif

39-6226AA.gif

104 ms

63.gif

63.gif

198 ms

156 ms

track_website.cgi

track_website.cgi

314 ms

spacer_top_pink.gif

spacer_top_pink.gif

28 ms

bg_header_pink.gif

bg_header_pink.gif

29 ms

leftsidelogos_pink.jpg

leftsidelogos_pink.jpg

30 ms

logo_ftd_plain.gif

logo_ftd_plain.gif

32 ms

bg_header_lang_pink.gif

bg_header_lang_pink.gif

32 ms

bg_topnav_3_pink.gif

bg_topnav_3_pink.gif

30 ms

clear.gif

clear.gif

30 ms

icon_home_pink.gif

icon_home_pink.gif

150 ms

button_home_3_pink.gif

button_home_3_pink.gif

31 ms

seperator_pink.gif

seperator_pink.gif

33 ms

button_aboutus_3_pink.gif

button_aboutus_3_pink.gif

33 ms

button_contactus_3_pink.gif

button_contactus_3_pink.gif

38 ms

button_areasweserve_3_pink.gif

button_areasweserve_3_pink.gif

34 ms

button_our_guarantee_3_pink.gif

button_our_guarantee_3_pink.gif

34 ms

button_login_3_pink.gif

button_login_3_pink.gif

34 ms

button_cart_3_pink.gif

button_cart_3_pink.gif

34 ms

icon_cart_pink.gif

icon_cart_pink.gif

170 ms

bg_innerside_topleft_pink.gif

bg_innerside_topleft_pink.gif

35 ms

bg_innerpage_topright_pink.gif

bg_innerpage_topright_pink.gif

35 ms

bg_innerpage_pink.gif

bg_innerpage_pink.gif

38 ms

spacer_leftnav.gif

spacer_leftnav.gif

35 ms

button_search_3_pink.gif

button_search_3_pink.gif

36 ms

icon_search.gif

icon_search.gif

36 ms

button_go_pink.gif

button_go_pink.gif

37 ms

icon_holidays_pink.gif

icon_holidays_pink.gif

37 ms

button_holidays_3_pink.gif

button_holidays_3_pink.gif

37 ms

bulletside.gif

bulletside.gif

42 ms

icon_occasions_pink.gif

icon_occasions_pink.gif

40 ms

button_occasions_3_pink.gif

button_occasions_3_pink.gif

38 ms

dot-nav-right.gif

dot-nav-right.gif

37 ms

icon_products_pink.gif

icon_products_pink.gif

38 ms

button_products_3_pink.gif

button_products_3_pink.gif

38 ms

icon_site_services_pink.gif

icon_site_services_pink.gif

39 ms

button_site_services_3_pink.gif

button_site_services_3_pink.gif

40 ms

icon_globe.gif

icon_globe.gif

40 ms

spacer.gif

spacer.gif

164 ms

157 ms

155 ms

145 ms

144 ms

161 ms

358 ms

293 ms

1369 ms

squ_border_pink_02.gif

squ_border_pink_02.gif

240 ms

squ_border_pink_01.gif

squ_border_pink_01.gif

234 ms

squ_border_pink_03.gif

squ_border_pink_03.gif

235 ms

squ_border_pink_04.gif

squ_border_pink_04.gif

308 ms

squ_border_pink_06.gif

squ_border_pink_06.gif

310 ms

squ_border_pink_08.gif

squ_border_pink_08.gif

317 ms

squ_border_pink_07.gif

squ_border_pink_07.gif

367 ms

squ_border_pink_09.gif

squ_border_pink_09.gif

381 ms

email_capture_1_pink.jpg

email_capture_1_pink.jpg

383 ms

_FTD39-6226AA.js

_FTD39-6226AA.js

374 ms

float.js

float.js

33 ms

s-code-contents-bf919ebc8bd5fd7b810d08b6196a19e9c94bee07.js

s-code-contents-bf919ebc8bd5fd7b810d08b6196a19e9c94bee07.js

28 ms

back-mini-icon-br.png

back-mini-icon-br.png

221 ms

white-mini-icon-br.gif

white-mini-icon-br.gif

371 ms

button_international_3_pink.gif

button_international_3_pink.gif

28 ms

top_msg_ban_pink.gif

top_msg_ban_pink.gif

32 ms

promo_top_bg.gif

promo_top_bg.gif

29 ms

promo_middle_bg.gif

promo_middle_bg.gif

25 ms

button_ordernow_pink.gif

button_ordernow_pink.gif

26 ms

button_ordernow_pink.gif

button_ordernow_pink.gif

24 ms

promo_bottom_bg.gif

promo_bottom_bg.gif

25 ms

button_submit_pink.gif

button_submit_pink.gif

25 ms

bg_innerside_bottomleft_pink.gif

bg_innerside_bottomleft_pink.gif

25 ms

bg_innerpage_bottomright_pink.gif

bg_innerpage_bottomright_pink.gif

25 ms

bg_footer_pink.gif

bg_footer_pink.gif

24 ms

spacer_bottom_pink.gif

spacer_bottom_pink.gif

26 ms

232 ms

jquery.noconflict.js

jquery.noconflict.js

4 ms

index.html

index.html

321 ms

s2594415983650

s2594415983650

39 ms

index.html

index.html

315 ms

index.html

index.html

754 ms

track_website.cgi

track_website.cgi

139 ms

SEO Factors

5thavefloral.rtrk.com SEO score

0

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise 5thavefloral.rtrk.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 5thavefloral.rtrk.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

5thavefloral.rtrk.com

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