Tools & Wizards About Us

Report Summary

  • 7

    Performance

    Renders faster than
    22% of other websites

  • 62

    Accessibility

    Visual factors better than
    that of 28% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

camelia.ae

Camelia Flowers - Fresh flowers delivery in Abu Dhabi

Page Load Speed

11.9 sec in total

First Response

2 sec

Resources Loaded

8.5 sec

Page Rendered

1.4 sec

About Website

Visit camelia.ae now to see the best up-to-date Camelia content for India and also check out these interesting facts you probably never knew about camelia.ae

Discover the finest selection of flowers in the UAE at Camelia Flowers. From elegant bouquets to stunning arrangements, delivering happiness with every bloom.

Visit camelia.ae

Key Findings

We analyzed Camelia.ae page load time and found that the first response time was 2 sec and then it took 9.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

camelia.ae performance score

7

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.4 s

70/100

10%

LCP (Largest Contentful Paint)

Value40.7 s

0/100

25%

SI (Speed Index)

Value26.9 s

0/100

10%

TBT (Total Blocking Time)

Value4,610 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value1.985

0/100

15%

TTI (Time to Interactive)

Value35.3 s

0/100

10%

Network Requests Diagram

camelia.ae

2015 ms

camelia-logo.png

291 ms

logo.png

307 ms

box_shadow.png

400 ms

dummy.png

396 ms

Our browser made a total of 110 requests to load all elements on the main page. We found that 90% of them (99 requests) were addressed to the original Camelia.ae, 2% (2 requests) were made to Code.jquery.com and 2% (2 requests) were made to Googletagmanager.com. The less responsive or slowest element that took the longest time to load (2 sec) belongs to the original domain Camelia.ae.

Page Optimization Overview & Recommendations

Page size can be reduced by 881.4 kB (4%)

Content Size

24.2 MB

After Optimization

23.3 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Camelia.ae main page is 24.2 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. Only a small number of websites need less resources to load. Images take 23.2 MB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 355.5 kB

  • Original 427.7 kB
  • After minification 422.1 kB
  • After compression 72.3 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 355.5 kB or 83% of the original size.

Image Optimization

-2%

Potential reduce by 523.9 kB

  • Original 23.2 MB
  • After minification 22.7 MB

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. Camelia images are well optimized though.

JavaScript Optimization

-0%

Potential reduce by 2.0 kB

  • Original 538.6 kB
  • After minification 538.6 kB
  • After compression 536.6 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 27 B

  • Original 36.9 kB
  • After minification 36.9 kB
  • After compression 36.9 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. Camelia.ae has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 30 (33%)

Requests Now

90

After Optimization

60

  • Images
  • JavaScript
  • CSS

The browser has sent 90 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Camelia. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 23 to 1 for JavaScripts and from 9 to 1 for CSS and as a result speed up the page load time.

Network Requests Diagram

Accessibility Review

camelia.ae accessibility score

62

Accessibility Issues

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

High

[aria-*] attributes do not match their roles

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

High

Buttons do not have an accessible name

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

Contrast

These are opportunities to improve the legibility of your content.

Impact

Issue

High

Background and foreground colors do not have a sufficient contrast ratio.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

[id] attributes on active, focusable elements are not unique

High

Heading elements are not in a sequentially-descending order

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

camelia.ae best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

camelia.ae SEO score

86

Search Engine Optimization Advices

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

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

High

Document uses legible font sizes

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Camelia.ae 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 Camelia.ae 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.

Social Sharing Optimization

Open Graph description is not detected on the main page of Camelia. 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: