Tools & Wizards About Us
seelog.com screenshot

Report Summary

  • 87

    Performance

    Renders faster than
    89% of other websites

  • 57

    Accessibility

    Visual factors better than
    that of 24% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 58

    SEO

    Google-friendlier than
    21% of websites

seelog.com

SeeLog : Outil de mesure d'audience de mesure fréquentation / compteur audience / mesure audience

Page Load Speed

647 ms in total

First Response

168 ms

Resources Loaded

374 ms

Page Rendered

105 ms

seelog.com screenshot

About Website

Welcome to seelog.com homepage info - get ready to check See Log best content right away, or after learning these important things about seelog.com

SeeLog : Analyse de la fréquentation de votre site internet / mesure d'audience et de fréquentation, compteur

Visit seelog.com

Key Findings

We analyzed Seelog.com page load time and found that the first response time was 168 ms and then it took 479 ms to load all DOM resources and completely render a web page. This is quite a good result, as only 10% of websites can load faster.

Performance Metrics

seelog.com performance score

87

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value0.9 s

100/100

10%

LCP (Largest Contentful Paint)

Value4.1 s

47/100

25%

SI (Speed Index)

Value1.0 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0.009

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

seelog.com

168 ms

seelog.css

17 ms

AC_RunActiveContent.js

30 ms

fonction.js

114 ms

fond_site.jpg

16 ms

Our browser made a total of 54 requests to load all elements on the main page. We found that all of those requests were addressed to Seelog.com and no external sources were called. The less responsive or slowest element that took the longest time to load (168 ms) belongs to the original domain Seelog.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 21.0 kB (29%)

Content Size

72.4 kB

After Optimization

51.4 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Seelog.com main page is 72.4 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. 15% of websites need less resources to load. Images take 45.6 kB which makes up the majority of the site volume.

HTML Optimization

-83%

Potential reduce by 20.2 kB

  • Original 24.4 kB
  • After minification 18.7 kB
  • After compression 4.2 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 5.7 kB, which is 23% 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 20.2 kB or 83% of the original size.

Image Optimization

-1%

Potential reduce by 401 B

  • Original 45.6 kB
  • After minification 45.2 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. See Log images are well optimized though.

JavaScript Optimization

-20%

Potential reduce by 329 B

  • Original 1.6 kB
  • After minification 1.6 kB
  • After compression 1.3 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 329 B or 20% of the original size.

CSS Optimization

-11%

Potential reduce by 81 B

  • Original 735 B
  • After minification 735 B
  • After compression 654 B

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. Seelog.com needs all CSS files to be minified and compressed as it can save up to 81 B or 11% of the original size.

Requests Breakdown

Number of requests can be reduced by 22 (42%)

Requests Now

53

After Optimization

31

  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

seelog.com

seelog.com

168 ms

seelog.css

seelog.css

17 ms

AC_RunActiveContent.js

AC_RunActiveContent.js

30 ms

fonction.js

fonction.js

114 ms

fond_site.jpg

fond_site.jpg

16 ms

bout_01_1.gif

bout_01_1.gif

16 ms

sep_01.gif

sep_01.gif

34 ms

bout_02_1.gif

bout_02_1.gif

31 ms

sep_02.gif

sep_02.gif

31 ms

bout_03_1.gif

bout_03_1.gif

32 ms

sep_03.gif

sep_03.gif

31 ms

bout_04_1.gif

bout_04_1.gif

32 ms

sep_04.gif

sep_04.gif

44 ms

bout_05_1.gif

bout_05_1.gif

45 ms

sep_05.gif

sep_05.gif

45 ms

bout_06_1.gif

bout_06_1.gif

47 ms

sep_06.gif

sep_06.gif

45 ms

bout_07_1.gif

bout_07_1.gif

46 ms

sep_08.gif

sep_08.gif

58 ms

bout_09_1.gif

bout_09_1.gif

59 ms

spacer.gif

spacer.gif

59 ms

bdr_g_01.gif

bdr_g_01.gif

59 ms

bdr_g_02.jpg

bdr_g_02.jpg

60 ms

accueil_01.jpg

accueil_01.jpg

75 ms

accueil_02.gif

accueil_02.gif

72 ms

fleche_orange.gif

fleche_orange.gif

72 ms

bout_voir_tout_fonc_01.gif

bout_voir_tout_fonc_01.gif

73 ms

bdr_g_03.gif

bdr_g_03.gif

73 ms

bdr_g_04.jpg

bdr_g_04.jpg

74 ms

accueil_04.gif

accueil_04.gif

86 ms

bdr_g_05.gif

bdr_g_05.gif

87 ms

logo_vrdci.png

logo_vrdci.png

87 ms

redim_bleu.gif

redim_bleu.gif

18 ms

cot_g_01.jpg

cot_g_01.jpg

15 ms

cot_g_02.gif

cot_g_02.gif

16 ms

cot_g_03.gif

cot_g_03.gif

17 ms

int_01.gif

int_01.gif

18 ms

accueil_03.jpg

accueil_03.jpg

18 ms

int_02.gif

int_02.gif

29 ms

bdr_g_04b.gif

bdr_g_04b.gif

30 ms

fond_int.jpg

fond_int.jpg

30 ms

cot_g_04.gif

cot_g_04.gif

31 ms

int_04.gif

int_04.gif

31 ms

bout_voir_tout_fonc_02.gif

bout_voir_tout_fonc_02.gif

16 ms

bout_01_2.gif

bout_01_2.gif

16 ms

bout_02_2.gif

bout_02_2.gif

16 ms

bout_03_2.gif

bout_03_2.gif

17 ms

bout_04_2.gif

bout_04_2.gif

16 ms

bout_05_2.gif

bout_05_2.gif

16 ms

bout_06_2.gif

bout_06_2.gif

17 ms

bout_07_2.gif

bout_07_2.gif

30 ms

bout_08_2.gif

bout_08_2.gif

30 ms

bout_09_2.gif

bout_09_2.gif

30 ms

flag_us_2.gif

flag_us_2.gif

31 ms

Accessibility Review

seelog.com accessibility score

57

Accessibility Issues

Internationalization and localization

These are opportunities to improve the interpretation of your content by users in different locales.

Impact

Issue

High

<html> element does not have a [lang] attribute

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

Image elements do not have [alt] attributes

High

Links do not have a discernible name

High

<object> elements do not have alternate text

Best Practices

seelog.com 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

SEO Factors

seelog.com SEO score

58

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

Image elements do not have [alt] attributes

High

Document uses plugins

Language and Encoding

  • Language Detected

    FR

  • Language Claimed

    N/A

  • Encoding

    ISO-8859-1

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Seelog.com can be misinterpreted by Google and other search engines. Our service has detected that French 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 Seelog.com main page’s claimed encoding is iso-8859-1. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.

Social Sharing Optimization

seelog.com

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