Tools & Wizards About Us
philippineroses.com screenshot

Report Summary

  • 65

    Performance

    Renders faster than
    78% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 36% of websites

  • 50

    Best Practices

    More advanced features
    available than in
    19% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

philippineroses.com

***** -  Quezon City, Manila, Kalookan (Caloocan), Davao, Cebu, Zamboanga, Pasig, Valenzuela, Las Pinas, Antipolo, Taguig (Tagig), Cagayan de Oro, Par...

Page Load Speed

1.5 sec in total

First Response

197 ms

Resources Loaded

976 ms

Page Rendered

279 ms

philippineroses.com screenshot

About Website

Click here to check amazing Philippineroses content. Otherwise, check out these important facts you probably never knew about philippineroses.com

***** -

Visit philippineroses.com

Key Findings

We analyzed Philippineroses.com page load time and found that the first response time was 197 ms and then it took 1.3 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 25% of websites can load faster.

Performance Metrics

philippineroses.com performance score

65

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

72/100

10%

LCP (Largest Contentful Paint)

Value4.8 s

31/100

25%

SI (Speed Index)

Value2.7 s

96/100

10%

TBT (Total Blocking Time)

Value310 ms

77/100

30%

CLS (Cumulative Layout Shift)

Value0.161

72/100

15%

TTI (Time to Interactive)

Value5.8 s

67/100

10%

Network Requests Diagram

philippineroses.com

197 ms

philippineroses.com

229 ms

bootstrap.min.css

129 ms

jquery-3.4.1.min.js

162 ms

bootstrap.min.js

137 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 25% of them (18 requests) were addressed to the original Philippineroses.com, 74% (54 requests) were made to Floristwide.com and 1% (1 request) were made to Translate.google.com. The less responsive or slowest element that took the longest time to load (349 ms) relates to the external source Floristwide.com.

Page Optimization Overview & Recommendations

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

Content Size

1.5 MB

After Optimization

1.1 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Philippineroses.com main page is 1.5 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. 55% of websites need less resources to load. Images take 991.9 kB which makes up the majority of the site volume.

HTML Optimization

-89%

Potential reduce by 116.2 kB

  • Original 130.6 kB
  • After minification 84.5 kB
  • After compression 14.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 46.1 kB, which is 35% 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 116.2 kB or 89% of the original size.

Image Optimization

-1%

Potential reduce by 12.5 kB

  • Original 991.9 kB
  • After minification 979.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. Philippineroses images are well optimized though.

JavaScript Optimization

-68%

Potential reduce by 165.0 kB

  • Original 241.0 kB
  • After minification 233.1 kB
  • After compression 76.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 165.0 kB or 68% of the original size.

CSS Optimization

-85%

Potential reduce by 138.6 kB

  • Original 163.8 kB
  • After minification 146.4 kB
  • After compression 25.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. Philippineroses.com needs all CSS files to be minified and compressed as it can save up to 138.6 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 11 (15%)

Requests Now

71

After Optimization

60

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

philippineroses.com

philippineroses.com

197 ms

philippineroses.com

philippineroses.com

229 ms

bootstrap.min.css

bootstrap.min.css

129 ms

jquery-3.4.1.min.js

jquery-3.4.1.min.js

162 ms

bootstrap.min.js

bootstrap.min.js

137 ms

JScript.js

JScript.js

108 ms

Style.css

Style.css

116 ms

default-responsive.css

default-responsive.css

144 ms

jquery.min.js

jquery.min.js

192 ms

jcarousellite1.js

jcarousellite1.js

145 ms

jqueryeasing1.js

jqueryeasing1.js

153 ms

fadeslideshow.js

fadeslideshow.js

186 ms

jquery.dropdown.js

jquery.dropdown.js

187 ms

dropdown.css

dropdown.css

187 ms

element.js

element.js

40 ms

Philippineroses.gif

Philippineroses.gif

167 ms

view-cart.png

view-cart.png

170 ms

search.png

search.png

166 ms

tracking.png

tracking.png

168 ms

ard_tri_rd.gif

ard_tri_rd.gif

169 ms

menu_homepage.jpg

menu_homepage.jpg

170 ms

8826.jpg

8826.jpg

215 ms

ordernowimage_s.jpg

ordernowimage_s.jpg

190 ms

8817.jpg

8817.jpg

216 ms

bestvalue.jpg

bestvalue.jpg

224 ms

8565.jpg

8565.jpg

223 ms

8818.jpg

8818.jpg

226 ms

designerschoice.jpg

designerschoice.jpg

239 ms

designerschoicepremium.jpg

designerschoicepremium.jpg

241 ms

designerschoicedeluxe.jpg

designerschoicedeluxe.jpg

272 ms

8805.jpg

8805.jpg

251 ms

rosesblackwrapfreebear.jpg

rosesblackwrapfreebear.jpg

279 ms

7860.jpg

7860.jpg

256 ms

8263.jpg

8263.jpg

271 ms

8787.jpg

8787.jpg

272 ms

8825.jpg

8825.jpg

279 ms

8194.jpg

8194.jpg

285 ms

9026.jpg

9026.jpg

300 ms

8600.jpg

8600.jpg

299 ms

8750.jpg

8750.jpg

297 ms

7240.jpg

7240.jpg

308 ms

7811.jpg

7811.jpg

309 ms

7731.jpg

7731.jpg

314 ms

8546.jpg

8546.jpg

325 ms

8513.jpg

8513.jpg

326 ms

8710.jpg

8710.jpg

325 ms

floristwide.gif

floristwide.gif

338 ms

satisfaction.gif

satisfaction.gif

337 ms

servicerating.jpg

servicerating.jpg

342 ms

horizontal_solution_PPeCheck.gif

horizontal_solution_PPeCheck.gif

349 ms

close.png

close.png

131 ms

philippineroses.com

philippineroses.com

86 ms

tn_photo001.jpg

tn_photo001.jpg

226 ms

QuickView.png

QuickView.png

36 ms

loading.gif

loading.gif

38 ms

tn_photo002.jpg

tn_photo002.jpg

189 ms

tn_photo003.jpg

tn_photo003.jpg

203 ms

tn_photo004.jpg

tn_photo004.jpg

202 ms

tn_photo005.jpg

tn_photo005.jpg

207 ms

tn_photo006.jpg

tn_photo006.jpg

209 ms

tn_photo007.jpg

tn_photo007.jpg

209 ms

tn_photo008.jpg

tn_photo008.jpg

190 ms

tn_photo009.jpg

tn_photo009.jpg

182 ms

tn_photo010.jpg

tn_photo010.jpg

182 ms

tn_photo011.jpg

tn_photo011.jpg

182 ms

tn_photo012.jpg

tn_photo012.jpg

180 ms

tn_photo013.jpg

tn_photo013.jpg

178 ms

tn_photo014.jpg

tn_photo014.jpg

166 ms

tn_photo015.jpg

tn_photo015.jpg

184 ms

tn_photo016.jpg

tn_photo016.jpg

174 ms

tn_photo017.jpg

tn_photo017.jpg

175 ms

tn_photo018.jpg

tn_photo018.jpg

158 ms

tn_photo019.jpg

tn_photo019.jpg

162 ms

Accessibility Review

philippineroses.com accessibility score

71

Accessibility Issues

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

Image elements do not have [alt] attributes

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.

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

philippineroses.com best practices score

50

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

Displays images with incorrect aspect ratio

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

philippineroses.com SEO score

83

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

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Philippineroses.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 Philippineroses.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

philippineroses.com

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