1.7 sec in total
57 ms
1.4 sec
212 ms
Visit pacificflorist.com now to see the best up-to-date Pacific Florist content and also check out these interesting facts you probably never knew about pacificflorist.com
Best wedding flower and gift selection, same day flower delivery available in Toronto. No hidden fee and best value
Visit pacificflorist.comWe analyzed Pacificflorist.com page load time and found that the first response time was 57 ms and then it took 1.7 sec to load all DOM resources and completely render a web page. This is quite a good result, as only 35% of websites can load faster.
pacificflorist.com performance score
name
value
score
weighting
Value2.3 s
76/100
10%
Value8.5 s
1/100
25%
Value7.5 s
26/100
10%
Value250 ms
84/100
30%
Value0.222
56/100
15%
Value16.5 s
5/100
10%
57 ms
13 ms
19 ms
37 ms
38 ms
Our browser made a total of 47 requests to load all elements on the main page. We found that 4% of them (2 requests) were addressed to the original Pacificflorist.com, 38% (18 requests) were made to Img1.wsimg.com and 23% (11 requests) were made to Nebula.wsimg.com. The less responsive or slowest element that took the longest time to load (742 ms) relates to the external source Facebook.com.
Page size can be reduced by 211.9 kB (6%)
3.7 MB
3.5 MB
In fact, the total size of Pacificflorist.com main page is 3.7 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 3.4 MB which makes up the majority of the site volume.
Potential reduce by 42.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. 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 42.2 kB or 78% of the original size.
Potential reduce by 37.8 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. Pacific Florist images are well optimized though.
Potential reduce by 65.9 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 65.9 kB or 40% of the original size.
Potential reduce by 66.0 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. Pacificflorist.com needs all CSS files to be minified and compressed as it can save up to 66.0 kB or 78% of the original size.
Number of requests can be reduced by 23 (53%)
43
20
The browser has sent 43 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Pacific Florist. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 24 to 1 for JavaScripts and as a result speed up the page load time.
www.pacificflorist.com
57 ms
site.css
13 ms
duel.js
19 ms
scc-c2.min.js
37 ms
jq.js
38 ms
11b30bec1aaf3bc57fd4e44975abe397
25 ms
media.gallery.js
30 ms
facebookSDKHelper.js
28 ms
cookiemanager.js
27 ms
iebackground.js
27 ms
bd19acd440367289dd0c55ada2656863
159 ms
160817d786eb367b40c42e19a9dea0fa
189 ms
106eb693d717762fcb29c4abe0424885
315 ms
d2406002858ddef339509f6df2b4a75e
396 ms
67dae4333302bc953448605aebeb6b27
374 ms
c48eccda2704c36b5ee040ce05f0c37b
177 ms
util.fbSDKLoader.js
17 ms
util.window.js
20 ms
util.instances.js
17 ms
util.model.js
18 ms
documentHelper.js
16 ms
helper.js
98 ms
growl.js
98 ms
e22fabb9c0aae29d304a6a5200cb9554
608 ms
dg4n_p3sv6gCJkwzT6RXiJwu.woff
45 ms
S6uyw4BMUTPHjx4wWA.woff
10 ms
buEzpo6gcdjy0EiZMBUG4C0f-w.woff
7 ms
browser.js
5 ms
sf.core.pkg.js
13 ms
app.css
13 ms
sdk.js
29 ms
sdk.js
6 ms
29 ms
page.php
742 ms
5e6dd9722ee7a5ca782a0c7d821238e1
204 ms
62c5edc2bc165e61646135c57a1cd3a3
524 ms
9b9b175542edc5ce348e1703574f5448
402 ms
w-Kbjwch27U.css
17 ms
Uq3QOVza5tw.js
24 ms
teTZ2tZqwkq.js
53 ms
BECqV_OB-Tv.js
54 ms
xNa_5SPtPNu.js
53 ms
q4SZVAjzsaO.js
61 ms
p55HfXW__mM.js
60 ms
307340224_518335413630077_8209944248743576537_n.jpg
34 ms
307039577_518335416963410_6997289733718363733_n.jpg
10 ms
UXtr_j2Fwe-.png
8 ms
pacificflorist.com accessibility score
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
Buttons do not have an accessible name
Image elements do not have [alt] attributes
Links do not have a discernible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
pacificflorist.com best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Serves images with low resolution
General
Impact
Issue
Detected JavaScript libraries
Page has valid source maps
pacificflorist.com SEO score
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Pacificflorist.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 Pacificflorist.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.
pacificflorist.com
Open Graph data is detected on the main page of Pacific Florist. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: