Tools & Wizards About Us
raicem.github.io screenshot

Report Summary

  • 66

    Performance

    Renders faster than
    79% of other websites

  • 81

    Accessibility

    Visual factors better than
    that of 51% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    80% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

raicem.github.io

blog.cemunalan.com.tr

Page Load Speed

72 ms in total

First Response

16 ms

Resources Loaded

56 ms

Page Rendered

0 ms

raicem.github.io screenshot

About Website

Visit raicem.github.io now to see the best up-to-date Raicem Github content for China and also check out these interesting facts you probably never knew about raicem.github.io

Visit raicem.github.io

Key Findings

We analyzed Raicem.github.io page load time and found that the first response time was 16 ms and then it took 56 ms to load all DOM resources and completely render a web page. This is an excellent result, as only a small number of websites can load faster.

Performance Metrics

raicem.github.io performance score

66

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.5 s

14/100

10%

LCP (Largest Contentful Paint)

Value5.6 s

18/100

25%

SI (Speed Index)

Value4.5 s

72/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value4.5 s

82/100

10%

Network Requests Diagram

raicem.github.io

16 ms

raicem.github.io

37 ms

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

Page Optimization Overview & Recommendations

Page size can be reduced by 67 B (29%)

Content Size

230 B

After Optimization

163 B

  • HTML

In fact, the total size of Raicem.github.io main page is 230 B. This result falls within the top 5000 of lightweight and thus fast loading web pages. Only a small number of websites need less resources to load. HTML takes 230 B which makes up the majority of the site volume.

HTML Optimization

-29%

Potential reduce by 67 B

  • Original 230 B
  • After minification 224 B
  • After compression 163 B

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 67 B or 29% of the original size.

Requests Breakdown

We found no issues to fix!

Requests Now

0

After Optimization

0

Besides the initial HTML request, no CSS, Javascripts, AJAX or image files were requested in the course of web page rendering.

Network Requests Diagram

raicem.github.io

raicem.github.io

16 ms

raicem.github.io

raicem.github.io

37 ms

Accessibility Review

raicem.github.io accessibility score

81

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.

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

Best Practices

raicem.github.io best practices score

92

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

SEO Factors

raicem.github.io SEO score

83

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

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

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    TR

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Raicem.github.io can be misinterpreted by Google and other search engines. Our service has detected that Turkish is used on the page, and it does not match the claimed English language. Our system also found out that Raicem.github.io 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

raicem.github.io

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