Report Summary

  • 62

    Performance

    Renders faster than
    76% of other websites

  • 88

    Accessibility

    Visual factors better than
    that of 68% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 86

    SEO

    Google-friendlier than
    60% of websites

elixirweb.studio

WordPress Consultancy Services  | Elixir Web Studio

Page Load Speed

2.8 sec in total

First Response

176 ms

Resources Loaded

1.9 sec

Page Rendered

718 ms

About Website

Click here to check amazing Elixir Web content. Otherwise, check out these important facts you probably never knew about elixirweb.studio

We build WordPress websites that bring your business to life and get you results. Call 020 3633 5332 and tell us your story.

Visit elixirweb.studio

Key Findings

We analyzed Elixirweb.studio page load time and found that the first response time was 176 ms and then it took 2.6 sec to load all DOM resources and completely render a web page. This is a poor result, as 50% of websites can load faster.

Performance Metrics

elixirweb.studio performance score

62

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value3.7 s

29/100

10%

LCP (Largest Contentful Paint)

Value3.7 s

57/100

25%

SI (Speed Index)

Value5.2 s

59/100

10%

TBT (Total Blocking Time)

Value370 ms

71/100

30%

CLS (Cumulative Layout Shift)

Value0.072

96/100

15%

TTI (Time to Interactive)

Value8.5 s

37/100

10%

Network Requests Diagram

elixirweb.studio

176 ms

elixirweb.studio

422 ms

uc.js

58 ms

ma_customfonts.css

79 ms

style.min.css

158 ms

Our browser made a total of 84 requests to load all elements on the main page. We found that 62% of them (52 requests) were addressed to the original Elixirweb.studio, 21% (18 requests) were made to Elixirwebstudio.b-cdn.net and 15% (13 requests) were made to Embed.tawk.to. The less responsive or slowest element that took the longest time to load (714 ms) belongs to the original domain Elixirweb.studio.

Page Optimization Overview & Recommendations

Page size can be reduced by 208.7 kB (21%)

Content Size

974.7 kB

After Optimization

766.1 kB

In fact, the total size of Elixirweb.studio main page is 974.7 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. 50% of websites need less resources to load. Images take 462.6 kB which makes up the majority of the site volume.

HTML Optimization

-79%

Potential reduce by 96.9 kB

  • Original 122.5 kB
  • After minification 121.0 kB
  • After compression 25.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. 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 96.9 kB or 79% of the original size.

Image Optimization

-0%

Potential reduce by 7 B

  • Original 462.6 kB
  • After minification 462.6 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. Elixir Web images are well optimized though.

JavaScript Optimization

-39%

Potential reduce by 111.3 kB

  • Original 284.2 kB
  • After minification 284.2 kB
  • After compression 172.9 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 111.3 kB or 39% of the original size.

CSS Optimization

-0%

Potential reduce by 458 B

  • Original 105.4 kB
  • After minification 105.4 kB
  • After compression 105.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. Elixirweb.studio has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 57 (70%)

Requests Now

82

After Optimization

25

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

Accessibility Review

elixirweb.studio accessibility score

88

Accessibility Issues

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

Heading elements are not in a sequentially-descending order

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

Links do not have a discernible name

Best Practices

elixirweb.studio 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

Page has valid source maps

SEO Factors

elixirweb.studio SEO score

86

Search Engine Optimization Advices

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

Links do not have descriptive text

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

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 Elixirweb.studio 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 Elixirweb.studio 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 data is detected on the main page of Elixir Web. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: