Access may-we-meet-again.xobor.de. The 100 ~ May we meet again

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value9.7 s

0/100

25%

SI (Speed Index)

Value6.3 s

42/100

10%

TBT (Total Blocking Time)

Value280 ms

81/100

30%

CLS (Cumulative Layout Shift)

Value0.513

15/100

15%

TTI (Time to Interactive)

Value9.1 s

33/100

10%

may-we-meet-again.xobor.de

343 ms

style4312-tglobal-111-global-1.css

120 ms

jquery-1.7.1.min.js

298 ms

plugin4312.js

216 ms

script4312.js

318 ms

Our browser made a total of 97 requests to load all elements on the main page. We found that 6% of them (6 requests) were addressed to the original May-we-meet-again.xobor.de, 18% (17 requests) were made to Files.homepagemodules.de and 10% (10 requests) were made to Dmp.theadex.com. The less responsive or slowest element that took the longest time to load (1.5 sec) relates to the external source Files.homepagemodules.de.

Content Size

1.1 MB

After Optimization

966.4 kB

In fact, the total size of May-we-meet-again.xobor.de main page is 1.1 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. 55% of websites need less resources to load. Images take 961.1 kB which makes up the majority of the site volume.

HTML Optimization

-76%

Potential reduce by 32.3 kB

Original 42.3 kB
After minification 41.3 kB
After compression 10.0 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 32.3 kB or 76% of the original size.

Image Optimization

-8%

Potential reduce by 80.9 kB

Original 961.1 kB
After minification 880.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. May We Meet Again Xobor images are well optimized though.

JavaScript Optimization

-48%

Potential reduce by 68.3 kB

Original 143.0 kB
After minification 142.6 kB
After compression 74.6 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 68.3 kB or 48% of the original size.

CSS Optimization

-25%

Potential reduce by 516 B

Original 2.1 kB
After minification 2.1 kB
After compression 1.6 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. May-we-meet-again.xobor.de needs all CSS files to be minified and compressed as it can save up to 516 B or 25% of the original size.

Requests Now

After Optimization

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

Accessibility Issues

These are opportunities to improve the legibility of your content.

High

Background and foreground colors do not have a sufficient contrast ratio.

These are opportunities to improve the usage of ARIA in your application which may enhance the experience for users of assistive technology, like a screen reader.

High

ARIA IDs are not unique

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.

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

These are opportunities to improve keyboard navigation in your application.

High

Some elements have a [tabindex] value greater than 0

Areas of Improvement

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

High

Serves images with low resolution

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

Search Engine Optimization Advices

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

High

Links are not crawlable

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

High

Image elements do not have [alt] attributes

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/).

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

Language Detected

DE
Language Claimed

DE
Encoding

UTF-8

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

may-we-meet-again.xobor.de

Open Graph description is not detected on the main page of May We Meet Again Xobor. 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:

Report Summary

Performance

Accessibility

Best Practices

SEO

The 100 ~ May we meet again

Page Load Speed

First Response

Resources Loaded

Page Rendered

About Website

Key Findings

Performance Metrics

Measured Metrics

FCP (First Contentful Paint)

LCP (Largest Contentful Paint)

SI (Speed Index)

TBT (Total Blocking Time)

CLS (Cumulative Layout Shift)

TTI (Time to Interactive)

Network Requests Diagram

may-we-meet-again.xobor.de

style4312-tglobal-111-global-1.css

jquery-1.7.1.min.js

plugin4312.js

script4312.js

Page Optimization Overview & Recommendations

Content Size

After Optimization

HTML Optimization

Image Optimization

JavaScript Optimization

CSS Optimization

Requests Breakdown

Requests Now

After Optimization

Network Requests Diagram

may-we-meet-again.xobor.de

style4312-tglobal-111-global-1.css

jquery-1.7.1.min.js

plugin4312.js

script4312.js

advertisement.js

sdk.js

sdk.js

a_13_4e7a6ec9.jpg

vquiz42e.png

tumblr_n6wn6vrpdi1r4bsjno3_250.gif

line2ykhv8x9lr1.gif

xl16c.png

9p5ybnpe.png

xsuzvfn8.png

iqgw3m4d.png

a_1_0c9d5111.jpg

a_4_74074e60.gif

a_7_9cfa6bfa.gif

a_8_50ecfcc6.gif

a_9_33cd3ff3.gif

a_34.png

a_32.png

a_14_1d8fbb12.png

a_18_0c7f90f3.png

a_17_00750796.png

a_19_39ecbbca.png

a_25_5c7d84da.png

a_24_aaa51310.png

a_21_56c4e990.png

a_484.png

a_486.png

handler.php

svg-object_forumheaderleft-color1_B7B7B7-color2_272727-color3_FFF.png

svg-object_forumheaderright-color1_B7B7B7-color2_272727-color3_FFF.png

svg-object_forumfooterleft-color1_B7B7B7-color2_272727-color3_FFF.png

svg-object_forumfooterright-color1_B7B7B7-color2_272727-color3_FFF.png

plusone.js

xoborajs.php

cb=gapi.loaded_0

cb=gapi.loaded_1

fastbutton

postmessageRelay