6.7 sec in total
587 ms
6 sec
147 ms
Click here to check amazing Emily Andme content. Otherwise, check out these important facts you probably never knew about emilyandme.co.uk
The leading Kent wedding florist for award winning florals. Contact us tor truly outstanding Wedding Flowers.
Visit emilyandme.co.ukWe analyzed Emilyandme.co.uk page load time and found that the first response time was 587 ms and then it took 6.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.
emilyandme.co.uk performance score
name
value
score
weighting
Value3.8 s
28/100
10%
Value5.2 s
24/100
25%
Value7.0 s
32/100
10%
Value90 ms
99/100
30%
Value0.368
29/100
15%
Value5.0 s
76/100
10%
587 ms
437 ms
116 ms
439 ms
450 ms
Our browser made a total of 88 requests to load all elements on the main page. We found that 73% of them (64 requests) were addressed to the original Emilyandme.co.uk, 25% (22 requests) were made to Cdn.website-start.de and 2% (2 requests) were made to 103.sb.mywebsite-editor.com. The less responsive or slowest element that took the longest time to load (3.4 sec) belongs to the original domain Emilyandme.co.uk.
Page size can be reduced by 80.2 kB (1%)
6.8 MB
6.7 MB
In fact, the total size of Emilyandme.co.uk main page is 6.8 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. 45% of websites need less resources to load. Images take 6.7 MB which makes up the majority of the site volume.
Potential reduce by 50.5 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 50.5 kB or 85% of the original size.
Potential reduce by 8.7 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. Emily Andme images are well optimized though.
Potential reduce by 19.3 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 19.3 kB or 42% of the original size.
Potential reduce by 1.7 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. Emilyandme.co.uk needs all CSS files to be minified and compressed as it can save up to 1.7 kB or 27% of the original size.
Number of requests can be reduced by 15 (18%)
83
68
The browser has sent 83 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Emily Andme. 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 8 to 1 for CSS and as a result speed up the page load time.
www.emilyandme.co.uk
587 ms
style.css
437 ms
theming.css
116 ms
web.css
439 ms
mobilenavigation.css
450 ms
logstate2-css.php
461 ms
logstate-js.php
478 ms
web.js
872 ms
web.bundle.js
468 ms
mobilenavigation.js
475 ms
758 ms
pfcsupport.js
540 ms
basic.css
585 ms
web.css
589 ms
logo.jpg
128 ms
thumb_76897506.jpeg
231 ms
thumb_76897507.jpeg
302 ms
thumb_76897508.jpeg
303 ms
thumb_76897509.jpeg
301 ms
thumb_76897510.jpeg
312 ms
thumb_76897511.jpeg
312 ms
thumb_76897512.jpeg
338 ms
thumb_76897513.jpeg
451 ms
thumb_76897514.jpeg
450 ms
thumb_76897515.jpeg
452 ms
thumb_76897516.jpeg
419 ms
thumb_76897517.jpeg
421 ms
thumb_76897518.jpeg
468 ms
thumb_76897519.jpeg
526 ms
thumb_76897520.jpeg
529 ms
thumb_76897521.jpeg
554 ms
cache_37962365.jpeg
686 ms
print.css
99 ms
thumb_76043307.jpeg
539 ms
thumb_76043308.jpeg
562 ms
thumb_76043309.jpeg
616 ms
thumb_76043310.jpg
614 ms
thumb_76043311.jpeg
796 ms
thumb_76043312.JPG
643 ms
thumb_76043313.PNG
672 ms
thumb_76043314.jpeg
726 ms
thumb_76043315.jpg
730 ms
thumb_76043316.PNG
761 ms
thumb_76043317.jpg
774 ms
thumb_76043318.jpeg
801 ms
thumb_76043319.jpg
837 ms
thumb_76043320.png
851 ms
thumb_76043321.PNG
877 ms
thumb_76043322.jpeg
918 ms
thumb_76043323.png
895 ms
thumb_76043324.jpeg
928 ms
Arimo-Regular.woff
915 ms
Arimo-Bold.woff
782 ms
SourceSansPro-Regular.woff
305 ms
SourceSansPro-Bold.woff
293 ms
facebook_big.png
105 ms
tumblr_big.png
173 ms
pinterest_big.png
208 ms
printer.gif
271 ms
order.js
309 ms
thumb_76043325.jpeg
867 ms
thumb_76043326.jpeg
763 ms
thumb_76043327.png
708 ms
thumb_76043328.png
730 ms
thumb_76043329.png
748 ms
thumb_76043330.png
750 ms
thumb_76043331.png
805 ms
thumb_76043332.png
769 ms
socialNetworkBar.js
100 ms
en_GB
142 ms
thumb_76043333.png
704 ms
thumb_76043334.jpg
724 ms
cache_76897506.jpeg
831 ms
cache_76897507.jpeg
1310 ms
cache_76897508.jpeg
1766 ms
cache_76897509.jpeg
1521 ms
cache_76897510.jpeg
1540 ms
cache_76897511.jpeg
1319 ms
cache_76897512.jpeg
1426 ms
cache_76897513.jpeg
1888 ms
cache_76897514.jpeg
3053 ms
cache_76897515.jpeg
2211 ms
cache_76897516.jpeg
1787 ms
cache_76897517.jpeg
2003 ms
cache_76897518.jpeg
3444 ms
cache_76897519.jpeg
2475 ms
cache_76897520.jpeg
2281 ms
cache_76897521.jpeg
2425 ms
emilyandme.co.uk accessibility score
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
[id] attributes on active, focusable elements are not unique
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.
emilyandme.co.uk 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
emilyandme.co.uk SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
robots.txt is not valid
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
EN
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Emilyandme.co.uk 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 Emilyandme.co.uk 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.
emilyandme.co.uk
Open Graph data is detected on the main page of Emily Andme. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: