1.3 sec in total
343 ms
630 ms
307 ms
Visit charlotte.com.qa now to see the best up-to-date Charlotte Com content and also check out these interesting facts you probably never knew about charlotte.com.qa
Visit charlotte.com.qaWe analyzed Charlotte.com.qa page load time and found that the first response time was 343 ms and then it took 937 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 15% of websites can load faster.
charlotte.com.qa performance score
name
value
score
weighting
Value1.9 s
88/100
10%
Value6.6 s
8/100
25%
Value3.3 s
91/100
10%
Value80 ms
99/100
30%
Value0.866
4/100
15%
Value5.0 s
76/100
10%
343 ms
48 ms
43 ms
29 ms
38 ms
Our browser made a total of 59 requests to load all elements on the main page. We found that 95% of them (56 requests) were addressed to the original Charlotte.com.qa, 3% (2 requests) were made to Fonts.googleapis.com and 2% (1 request) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (343 ms) belongs to the original domain Charlotte.com.qa.
Page size can be reduced by 202.1 kB (12%)
1.6 MB
1.4 MB
In fact, the total size of Charlotte.com.qa main page is 1.6 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. 60% of websites need less resources to load. Images take 1.4 MB which makes up the majority of the site volume.
Potential reduce by 23.6 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 4.8 kB, which is 17% 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 23.6 kB or 82% of the original size.
Potential reduce by 31.5 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. Charlotte Com images are well optimized though.
Potential reduce by 20.7 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 20.7 kB or 27% of the original size.
Potential reduce by 126.3 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. Charlotte.com.qa needs all CSS files to be minified and compressed as it can save up to 126.3 kB or 79% of the original size.
Number of requests can be reduced by 12 (22%)
55
43
The browser has sent 55 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Charlotte Com. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 5 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.
charlotte.com.qa
343 ms
bootstrap.min.css
48 ms
font-awesome.min.css
43 ms
css
29 ms
owl.carousel.css
38 ms
owl.theme.css
40 ms
owl.transitions.css
40 ms
style_charlotte.css
44 ms
aos.css
59 ms
jquery.min.js
92 ms
bootstrap.min.js
86 ms
aos.js
74 ms
main.js
74 ms
owl.carousel.js
75 ms
logo.png
76 ms
banner.jpg
199 ms
welcome_image.jpg
191 ms
chairman_img.jpg
88 ms
Charlotte%20Logo%20Gold-1.jpg
192 ms
Sweet1.jpg
188 ms
deep_impact_logo.jpg
189 ms
Capture2.png
190 ms
product_img.jpg
194 ms
product_img2.jpg
194 ms
erko-mellow1.jpg
192 ms
product_img4.jpg
194 ms
relkon1.jpg
195 ms
pasta1.jpg
199 ms
orion1.jpg
199 ms
oshee2.jpg
196 ms
Bazooka1.jpg
197 ms
cocon1.jpg
199 ms
zed2.jpg
200 ms
Aldiva1.png
201 ms
omypop1.jpg
201 ms
coffee1.jpg
220 ms
soya1.jpg
220 ms
pokka1.jpg
220 ms
carrefour_logo.jpg
191 ms
lulu_logo.jpg
188 ms
masskar.jpg
188 ms
quality.jpg
186 ms
css
13 ms
landmark.png
186 ms
movenpick.png
179 ms
7Aulp_0qiz-aVz7u3PJLcUMYOFnOkEk30e0.ttf
115 ms
intercontinental.png
157 ms
spinneys.png
155 ms
torch.png
158 ms
safari.png
159 ms
toystar.png
159 ms
food1.png
152 ms
wood.png
149 ms
fontawesome-webfont.woff
72 ms
glyphicons-halflings-regular.woff
85 ms
almeera.png
66 ms
send_icon.png
66 ms
power.png
67 ms
cd-top-arrow.svg
80 ms
charlotte.com.qa 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
ARIA input fields do not have accessible names
Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.
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
charlotte.com.qa 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
Browser errors were logged to the console
Page has valid source maps
charlotte.com.qa 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
EN
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Charlotte.com.qa 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 Charlotte.com.qa 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.
charlotte.com.qa
Open Graph description is not detected on the main page of Charlotte Com. 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: