Report Summary

  • 100

    Performance

    Renders faster than
    97% of other websites

  • 97

    Accessibility

    Visual factors better than
    that of 92% of websites

  • 92

    Best Practices

    More advanced features
    available than in
    81% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

Page Load Speed

7.3 sec in total

First Response

1.4 sec

Resources Loaded

5.1 sec

Page Rendered

808 ms

juliary.de screenshot

About Website

Click here to check amazing Juliary content for Germany. Otherwise, check out these important facts you probably never knew about juliary.de

Ein Lifestyleblog über Beauty, Fashion, Reisen, Ernährung und Dekoration. Geschrieben von Julia Lanea, Studentin im Bereich Multimedia und Kommunikation.

Visit juliary.de

Key Findings

We analyzed Juliary.de page load time and found that the first response time was 1.4 sec and then it took 5.9 sec to load all DOM resources and completely render a web page. This is a poor result, as 75% of websites can load faster.

Performance Metrics

juliary.de performance score

100

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value1.2 s

99/100

10%

LCP (Largest Contentful Paint)

Value1.2 s

100/100

25%

SI (Speed Index)

Value1.4 s

100/100

10%

TBT (Total Blocking Time)

Value0 ms

100/100

30%

CLS (Cumulative Layout Shift)

Value0

100/100

15%

TTI (Time to Interactive)

Value1.2 s

100/100

10%

Network Requests Diagram

www.juliary.de

1427 ms

wp-emoji-release.min.js

99 ms

ppibfi_pinterest.css

282 ms

simply-instagram.css

283 ms

simply-instagram-prettyPhoto.css

284 ms

Our browser made a total of 103 requests to load all elements on the main page. We found that 32% of them (33 requests) were addressed to the original Juliary.de, 15% (15 requests) were made to Static.xx.fbcdn.net and 9% (9 requests) were made to Scontent.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (2.2 sec) relates to the external source I1.wp.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 436.3 kB (18%)

Content Size

2.4 MB

After Optimization

1.9 MB

In fact, the total size of Juliary.de main page is 2.4 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. 75% of websites need less resources to load and that’s why Accessify’s recommendations for optimization and resource minification can be helpful for this project. Images take 1.8 MB which makes up the majority of the site volume.

HTML Optimization

-78%

Potential reduce by 52.3 kB

  • Original 66.8 kB
  • After minification 63.5 kB
  • After compression 14.5 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 52.3 kB or 78% of the original size.

Image Optimization

-0%

Potential reduce by 5.4 kB

  • Original 1.8 MB
  • After minification 1.8 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. Juliary images are well optimized though.

JavaScript Optimization

-66%

Potential reduce by 225.6 kB

  • Original 340.0 kB
  • After minification 324.2 kB
  • After compression 114.4 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 225.6 kB or 66% of the original size.

CSS Optimization

-82%

Potential reduce by 153.0 kB

  • Original 185.5 kB
  • After minification 165.9 kB
  • After compression 32.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. Juliary.de needs all CSS files to be minified and compressed as it can save up to 153.0 kB or 82% of the original size.

Requests Breakdown

Number of requests can be reduced by 47 (49%)

Requests Now

96

After Optimization

49

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

Accessibility Review

juliary.de accessibility score

97

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

Best Practices

juliary.de 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

SEO Factors

juliary.de SEO score

92

Search Engine Optimization Advices

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

    DE

  • Encoding

    UTF-8

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