Tools & Wizards About Us
elog.ms screenshot

Report Summary

  • 88

    Performance

    Renders faster than
    90% of other websites

  • 95

    Accessibility

    Visual factors better than
    that of 86% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 62

    SEO

    Google-friendlier than
    23% of websites

elog.ms

Mud Logging - Elog Ltd., It is real time data acquisition service provider

Page Load Speed

400 ms in total

First Response

36 ms

Resources Loaded

312 ms

Page Rendered

52 ms

elog.ms screenshot

About Website

Click here to check amazing Elog content. Otherwise, check out these important facts you probably never knew about elog.ms

Elog is real time data acquisition service, providing data monitoring and interpretation services to oil and gas companies. Elog provides real time access to exploratory and drilling data to the oil c...

Visit elog.ms

Key Findings

We analyzed Elog.ms page load time and found that the first response time was 36 ms and then it took 364 ms to load all DOM resources and completely render a web page. This is an excellent result, as only 5% of websites can load faster.

Performance Metrics

elog.ms performance score

88

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value2.5 s

67/100

10%

LCP (Largest Contentful Paint)

Value3.4 s

65/100

25%

SI (Speed Index)

Value2.5 s

98/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value2.5 s

98/100

10%

Network Requests Diagram

elog.ms

36 ms

www.elog.ms

145 ms

welcomestyles.css

14 ms

colourtag.css

51 ms

800.css

36 ms

Our browser made a total of 14 requests to load all elements on the main page. We found that 86% of them (12 requests) were addressed to the original Elog.ms, 14% (2 requests) were made to Google-analytics.com. The less responsive or slowest element that took the longest time to load (145 ms) belongs to the original domain Elog.ms.

Page Optimization Overview & Recommendations

Page size can be reduced by 74.5 kB (71%)

Content Size

105.0 kB

After Optimization

30.5 kB

  • HTML
  • JavaScript
  • CSS

In fact, the total size of Elog.ms main page is 105.0 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. Only 10% of websites need less resources to load. Javascripts take 67.5 kB which makes up the majority of the site volume.

HTML Optimization

-71%

Potential reduce by 4.6 kB

  • Original 6.5 kB
  • After minification 5.7 kB
  • After compression 1.9 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 845 B, which is 13% 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 4.6 kB or 71% of the original size.

JavaScript Optimization

-64%

Potential reduce by 43.4 kB

  • Original 67.5 kB
  • After minification 63.6 kB
  • After compression 24.1 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 43.4 kB or 64% of the original size.

CSS Optimization

-85%

Potential reduce by 26.4 kB

  • Original 30.9 kB
  • After minification 18.0 kB
  • After compression 4.5 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. Elog.ms needs all CSS files to be minified and compressed as it can save up to 26.4 kB or 85% of the original size.

Requests Breakdown

Number of requests can be reduced by 7 (58%)

Requests Now

12

After Optimization

5

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

elog.ms

elog.ms

36 ms

www.elog.ms

www.elog.ms

145 ms

welcomestyles.css

welcomestyles.css

14 ms

colourtag.css

colourtag.css

51 ms

800.css

800.css

36 ms

title_left.css

title_left.css

46 ms

sidebar_right.css

sidebar_right.css

42 ms

green.css

green.css

50 ms

javascript.js

javascript.js

61 ms

analytics.js

analytics.js

14 ms

Unit_Click.gif

Unit_Click.gif

37 ms

collect

collect

12 ms

print.css

print.css

16 ms

handheld.css

handheld.css

15 ms

Accessibility Review

elog.ms accessibility score

95

Accessibility Issues

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

<object> elements do not have alternate text

Best Practices

elog.ms best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Serves images with low resolution

General

Impact

Issue

Low

Detected JavaScript libraries

SEO Factors

elog.ms SEO score

62

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

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

High

Document uses plugins

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 Elog.ms 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 Elog.ms 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

elog.ms

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