1.7 sec in total
351 ms
1.2 sec
150 ms
Visit lordandberry.com now to see the best up-to-date Lord And Berry content for United States and also check out these interesting facts you probably never knew about lordandberry.com
Professional make-up products designed in Milan by the beauty & fashion industry’s finest artisans, designers & make up artists. Try our collections today.
Visit lordandberry.comWe analyzed Lordandberry.com page load time and found that the first response time was 351 ms and then it took 1.4 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.
lordandberry.com performance score
name
value
score
weighting
Value3.2 s
42/100
10%
Value5.3 s
22/100
25%
Value10.2 s
8/100
10%
Value580 ms
51/100
30%
Value0.003
100/100
15%
Value14.6 s
8/100
10%
351 ms
154 ms
156 ms
113 ms
117 ms
Our browser made a total of 61 requests to load all elements on the main page. We found that 90% of them (55 requests) were addressed to the original Lordandberry.com, 7% (4 requests) were made to Google-analytics.com and 2% (1 request) were made to Stats.g.doubleclick.net. The less responsive or slowest element that took the longest time to load (608 ms) belongs to the original domain Lordandberry.com.
Page size can be reduced by 246.9 kB (69%)
359.3 kB
112.4 kB
In fact, the total size of Lordandberry.com main page is 359.3 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. 70% of websites need less resources to load. Javascripts take 244.3 kB which makes up the majority of the site volume.
Potential reduce by 14.0 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 14.0 kB or 78% of the original size.
Potential reduce by 690 B
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. Obviously, Lord And Berry needs image optimization as it can save up to 690 B or 34% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.
Potential reduce by 151.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 151.5 kB or 62% of the original size.
Potential reduce by 80.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. Lordandberry.com needs all CSS files to be minified and compressed as it can save up to 80.7 kB or 85% of the original size.
Number of requests can be reduced by 16 (28%)
58
42
The browser has sent 58 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Lord And Berry. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 12 to 1 for JavaScripts and from 6 to 1 for CSS and as a result speed up the page load time.
lordandberry.com
351 ms
animations.css
154 ms
font-awesome.css
156 ms
gotham.css
113 ms
saharabodoni.css
117 ms
lordandberrylogo.css
115 ms
style.css
197 ms
jquery.js
259 ms
migrate.js
156 ms
bootstrap.js
205 ms
load.smartajax.js
173 ms
main.js
174 ms
1.jpg
247 ms
2.jpg
265 ms
3.jpg
279 ms
4.jpg
385 ms
backstage.jpg
298 ms
contacts.jpg
138 ms
franchising.jpg
313 ms
more.jpg
288 ms
mosaic.jpg
307 ms
mosaic2.jpg
322 ms
philosophy.jpg
530 ms
showroom.jpg
472 ms
story.jpg
489 ms
1.jpg
608 ms
2.jpg
346 ms
3.jpg
389 ms
4.jpg
407 ms
5.jpg
412 ms
6.jpg
451 ms
home-01.jpg
435 ms
home-02.jpg
458 ms
home-03.jpg
473 ms
home-04.jpg
481 ms
home-05.jpg
494 ms
1.jpg
497 ms
2.jpg
503 ms
3.jpg
511 ms
ga.js
12 ms
header.png
515 ms
gotham-book.woff
507 ms
lordberrylogo.woff
514 ms
fontawesome-webfont.woff
523 ms
__utm.gif
20 ms
row1col1.jpg
505 ms
row1col2.jpg
507 ms
row1col3.jpg
535 ms
row2col1.jpg
513 ms
row2col2.jpg
546 ms
analytics.js
12 ms
collect
72 ms
collect
34 ms
ga-audiences
42 ms
amplify.store.js
428 ms
history.adapter.jquery.js
322 ms
history.js
314 ms
history.html4.js
309 ms
smartajax.js
301 ms
saharabodoni.woff
301 ms
footer.png
294 ms
lordandberry.com accessibility score
ARIA
These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.
Impact
Issue
[role]s do not have all required [aria-*] attributes
[role]s are not contained by their required parent element
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
[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
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
Lists do not contain only <li> elements and script supporting elements (<script> and <template>).
List items (<li>) are not contained within <ul> or <ol> parent elements.
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.
lordandberry.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
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Browser errors were logged to the console
lordandberry.com SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
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
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 Lordandberry.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 Lordandberry.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.
lordandberry.com
Open Graph description is not detected on the main page of Lord And Berry. 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: