9.6 sec in total
1.7 sec
7.5 sec
351 ms
Welcome to imageflorist.com homepage info - get ready to check Image Florist best content for Malaysia right away, or after learning these important things about imageflorist.com
Malaysia Local flower shop in Desa Petaling, provide fast same day express flower delivery service within Kuala Lumpur KL, Petaling Jaya PJ, Subang Jaya SJ, Putrajaya and etc. Call, whatsapp, viber, ...
Visit imageflorist.comWe analyzed Imageflorist.com page load time and found that the first response time was 1.7 sec and then it took 7.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 85% of websites can load faster. This domain responded with an error, which can significantly jeopardize Imageflorist.com rating and web reputation
imageflorist.com performance score
name
value
score
weighting
Value6.8 s
2/100
10%
Value8.9 s
1/100
25%
Value9.3 s
13/100
10%
Value340 ms
74/100
30%
Value0.06
98/100
15%
Value9.6 s
29/100
10%
1691 ms
755 ms
1466 ms
909 ms
1978 ms
Our browser made a total of 105 requests to load all elements on the main page. We found that 78% of them (82 requests) were addressed to the original Imageflorist.com, 9% (9 requests) were made to Facebook.com and 2% (2 requests) were made to Apis.google.com. The less responsive or slowest element that took the longest time to load (3 sec) belongs to the original domain Imageflorist.com.
Page size can be reduced by 1.3 MB (64%)
2.0 MB
717.4 kB
In fact, the total size of Imageflorist.com main page is 2.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. 55% of websites need less resources to load. Javascripts take 1.2 MB which makes up the majority of the site volume.
Potential reduce by 123.9 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 33.1 kB, which is 22% 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 123.9 kB or 84% of the original size.
Potential reduce by 55.9 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. Image Florist images are well optimized though.
Potential reduce by 984.8 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 984.8 kB or 84% of the original size.
Potential reduce by 88.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. Imageflorist.com needs all CSS files to be minified and compressed as it can save up to 88.0 kB or 85% of the original size.
Number of requests can be reduced by 57 (57%)
100
43
The browser has sent 100 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Image 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 28 to 1 for JavaScripts and from 5 to 1 for CSS and as a result speed up the page load time.
imageflorist.com
1691 ms
Dimentions.css
755 ms
styles.css
1466 ms
widgets.css
909 ms
prototype.js
1978 ms
ccard.js
868 ms
validation.js
1068 ms
builder.js
1123 ms
effects.js
1745 ms
dragdrop.js
1530 ms
controls.js
1523 ms
slider.js
1431 ms
js.js
1755 ms
form.js
1810 ms
menu.js
1795 ms
plusone.js
88 ms
rightClick.js
1794 ms
rightClick.js
2002 ms
jquery-1.4.2.js
2986 ms
coin-slider.js
2111 ms
coin-slider.min.js
2197 ms
coin-slider-styles.css
2126 ms
WebResource.axd
1994 ms
ScriptResource.axd
2074 ms
ScriptResource.axd
2126 ms
ScriptResource.axd
2454 ms
ScriptResource.axd
2212 ms
ScriptResource.axd
2305 ms
ScriptResource.axd
2298 ms
ScriptResource.axd
2351 ms
cb=gapi.loaded_0
13 ms
BBS.aspx
129 ms
20px%20WhatsApp%2060122275700.png
801 ms
bg.gif
842 ms
logo.gif
878 ms
se.png
794 ms
login.png
820 ms
login-facebook.png
966 ms
WebResource.axd
1043 ms
ecard.gif
1173 ms
1323746417_email.png
1103 ms
eb9e8243-09bb-4363-8bb3-c46b0a2f1e11.jpg
2271 ms
df6f186c-dfc4-46b2-9b4e-feec8cd8bb91.jpg
2079 ms
105786f5-8ed8-41d8-af52-7839f9de5528.gif
1923 ms
62f0d4bb-6b63-42c4-a727-960ad4526cb3.gif
1972 ms
b543bc0b-1a27-4859-b6d6-01e8e739f301.gif
2004 ms
ImageRenderJpeg.ashx
1572 ms
ImageRenderJpeg.ashx
1820 ms
ImageRenderJpeg.ashx
2083 ms
ImageRenderJpeg.ashx
2303 ms
ImageRenderJpeg.ashx
2223 ms
ImageRenderJpeg.ashx
2257 ms
ImageRenderJpeg.ashx
2326 ms
ImageRenderJpeg.ashx
2417 ms
Submit.jpg
2556 ms
new-google-logo-knockoff.png
2748 ms
viber2.png
806 ms
all.js
23 ms
1324630819_google.png
2733 ms
116 ms
xd_arbiter.php
18 ms
xd_arbiter.php
36 ms
2cd7ee1d-f9cd-4b0b-be33-f423ad465b09.gif
2800 ms
0359d987-d44e-4a4a-b32d-e551c8f9d6c2.gif
2650 ms
BBS.aspx
118 ms
8fd76403-d7e8-4ac3-ad99-7020d43db8cf.gif
2680 ms
68e39f86-04f7-4c17-b178-1a213de0dd71.jpg
3039 ms
DBImage.ashx
78 ms
ga.js
43 ms
border_left.gif
1948 ms
border_right.gif
1959 ms
border_top.gif
1974 ms
border_bot.gif
2078 ms
left_top.gif
2107 ms
right_top.gif
2193 ms
left_bot.gif
2200 ms
right_bot.gif
2207 ms
bgflower.jpg
2742 ms
__utm.gif
72 ms
bg_box.gif
2287 ms
bg_title.gif
2391 ms
bg_title_top.gif
2453 ms
bg_title_bot.gif
2389 ms
bg_box_bot.gif
2430 ms
border_left_title.gif
2459 ms
border_right_title.gif
2560 ms
like.php
100 ms
like.php
141 ms
like.php
132 ms
like.php
148 ms
like.php
135 ms
like.php
161 ms
like.php
149 ms
like.php
204 ms
qeKvIRsJabD.js
30 ms
LVx-xkvaJ0b.png
22 ms
border_top_title.gif
2165 ms
border_bot_title.gif
1955 ms
left_top_title.gif
1946 ms
right_top_title.gif
1894 ms
left_bot_title.gif
1990 ms
right_bot_title.gif
1925 ms
devider_footer_2.gif
1933 ms
bg_footer.gif
1782 ms
print.css
236 ms
imageflorist.com accessibility score
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
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
<html> element does not have a [lang] attribute
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
Image elements do not have [alt] attributes
Links do not have a discernible name
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.
imageflorist.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
General
Impact
Issue
Detected JavaScript libraries
imageflorist.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Page is blocked from indexing
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
N/A
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Imageflorist.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 Imageflorist.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.
imageflorist.com
Open Graph description is not detected on the main page of Image Florist. 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: