Tools & Wizards About Us
namesforever.de screenshot

Report Summary

  • 21

    Performance

    Renders faster than
    39% of other websites

  • 71

    Accessibility

    Visual factors better than
    that of 37% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 92

    SEO

    Google-friendlier than
    75% of websites

namesforever.de

Personalisierter Schmuck | Names4ever

Page Load Speed

5.2 sec in total

First Response

333 ms

Resources Loaded

4.5 sec

Page Rendered

414 ms

namesforever.de screenshot

About Website

Welcome to namesforever.de homepage info - get ready to check Namesforever best content for Germany right away, or after learning these important things about namesforever.de

Personalisierter Schmuck für eine bleibende Erinnerung an unsere schönsten Momente und unsere Liebsten. Sehen Sie sich unsere Kollektion an.

Visit namesforever.de

Key Findings

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

Performance Metrics

namesforever.de performance score

21

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.3 s

18/100

10%

LCP (Largest Contentful Paint)

Value26.8 s

0/100

25%

SI (Speed Index)

Value11.1 s

6/100

10%

TBT (Total Blocking Time)

Value480 ms

59/100

30%

CLS (Cumulative Layout Shift)

Value0.854

4/100

15%

TTI (Time to Interactive)

Value20.6 s

2/100

10%

Network Requests Diagram

namesforever.de

333 ms

www.namesforever.de

818 ms

jquery-1.11.1.min.js

39 ms

Global

90 ms

language-strings

179 ms

Our browser made a total of 73 requests to load all elements on the main page. We found that 11% of them (8 requests) were addressed to the original Namesforever.de, 49% (36 requests) were made to Names4ever.azurewebsites.net and 14% (10 requests) were made to Static.xx.fbcdn.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Names4ever.azurewebsites.net.

Page Optimization Overview & Recommendations

Page size can be reduced by 125.6 kB (19%)

Content Size

675.8 kB

After Optimization

550.2 kB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Namesforever.de main page is 675.8 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. 45% of websites need less resources to load. Images take 516.4 kB which makes up the majority of the site volume.

HTML Optimization

-77%

Potential reduce by 28.6 kB

  • Original 37.3 kB
  • After minification 37.1 kB
  • After compression 8.6 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 28.6 kB or 77% of the original size.

Image Optimization

-4%

Potential reduce by 22.2 kB

  • Original 516.4 kB
  • After minification 494.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. Namesforever images are well optimized though.

JavaScript Optimization

-60%

Potential reduce by 46.7 kB

  • Original 77.8 kB
  • After minification 56.5 kB
  • After compression 31.0 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 46.7 kB or 60% of the original size.

CSS Optimization

-63%

Potential reduce by 28.0 kB

  • Original 44.4 kB
  • After minification 44.4 kB
  • After compression 16.4 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. Namesforever.de needs all CSS files to be minified and compressed as it can save up to 28.0 kB or 63% of the original size.

Requests Breakdown

Number of requests can be reduced by 35 (50%)

Requests Now

70

After Optimization

35

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

namesforever.de

namesforever.de

333 ms

www.namesforever.de

www.namesforever.de

818 ms

jquery-1.11.1.min.js

jquery-1.11.1.min.js

39 ms

Global

Global

90 ms

language-strings

language-strings

179 ms

main.min.css

main.min.css

1115 ms

names4ever.css

names4ever.css

1017 ms

font-awesome.min.css

font-awesome.min.css

645 ms

product-detail.min.css

product-detail.min.css

1032 ms

names4ever.js

names4ever.js

1321 ms

jquery.hoverIntent.min.js

jquery.hoverIntent.min.js

1016 ms

menu.min.js

menu.min.js

726 ms

product-detail.js

product-detail.js

1041 ms

home.min.css

home.min.css

1163 ms

home.js

home.js

1191 ms

fbds.js

fbds.js

225 ms

namesforever-logo-header.svg

namesforever-logo-header.svg

594 ms

winkelwagen.svg

winkelwagen.svg

570 ms

verisign-secured.svg

verisign-secured.svg

584 ms

banner01.jpg

banner01.jpg

493 ms

banner02.jpg

banner02.jpg

325 ms

banner03.jpg

banner03.jpg

347 ms

banner04.jpg

banner04.jpg

356 ms

banner05.jpg

banner05.jpg

344 ms

banner06.jpg

banner06.jpg

325 ms

banner08.jpg

banner08.jpg

468 ms

banner07.jpg

banner07.jpg

595 ms

banner09.jpg

banner09.jpg

641 ms

namesforever-logo-footer.svg

namesforever-logo-footer.svg

587 ms

trust-de.svg

trust-de.svg

654 ms

sdk.js

sdk.js

250 ms

analytics.js

analytics.js

152 ms

nl.png

nl.png

558 ms

be.png

be.png

577 ms

de.png

de.png

664 ms

at.png

at.png

669 ms

ch.png

ch.png

675 ms

en.png

en.png

684 ms

es.png

es.png

836 ms

checkbox.png

checkbox.png

785 ms

Update-client

Update-client

273 ms

language-strings

language-strings

184 ms

related-products

related-products

518 ms

Valentijn-Infinity-DE.jpg

Valentijn-Infinity-DE.jpg

1230 ms

icon-facebook.svg

icon-facebook.svg

846 ms

icon-youtube.svg

icon-youtube.svg

711 ms

icon-pinterest.svg

icon-pinterest.svg

806 ms

icon-copyright.svg

icon-copyright.svg

849 ms

DroidSans-webfont.svg

DroidSans-webfont.svg

1218 ms

DroidSans-webfont.woff

DroidSans-webfont.woff

943 ms

collect

collect

7 ms

collect

collect

107 ms

135 ms

89 ms

xd_arbiter.php

xd_arbiter.php

130 ms

8ae49f25882f47a1b482031e0df010b9

8ae49f25882f47a1b482031e0df010b9

97 ms

21 ms

like_box.php

like_box.php

140 ms

410ucuAGgaJ.css

410ucuAGgaJ.css

87 ms

tSbl8xBI27R.css

tSbl8xBI27R.css

107 ms

q68gy-v_YMF.js

q68gy-v_YMF.js

143 ms

FJmpeSpHpjS.js

FJmpeSpHpjS.js

178 ms

0wM5s1Khldu.js

0wM5s1Khldu.js

171 ms

1bNoFZUdlYZ.js

1bNoFZUdlYZ.js

170 ms

12662599_1018957524814122_6086477803804849774_n.jpg

12662599_1018957524814122_6086477803804849774_n.jpg

84 ms

1908449_805561019487108_2275001602765437679_n.jpg

1908449_805561019487108_2275001602765437679_n.jpg

42 ms

12705516_1684225865148794_3038699010898275409_n.jpg

12705516_1684225865148794_3038699010898275409_n.jpg

121 ms

12573790_113440942370062_1138902228090794854_n.jpg

12573790_113440942370062_1138902228090794854_n.jpg

83 ms

11295672_864260193611673_5643541378114511912_n.jpg

11295672_864260193611673_5643541378114511912_n.jpg

80 ms

wL6VQj7Ab77.png

wL6VQj7Ab77.png

20 ms

s7jcwEQH7Sx.png

s7jcwEQH7Sx.png

21 ms

I6-MnjEovm5.js

I6-MnjEovm5.js

19 ms

pQrUxxo5oQp.js

pQrUxxo5oQp.js

21 ms

Accessibility Review

namesforever.de accessibility score

71

Accessibility Issues

ARIA

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.

Impact

Issue

High

[aria-hidden="true"] elements contain focusable descendents

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

Buttons do not have an accessible name

High

<frame> or <iframe> elements do not have a title

High

Image elements do not have [alt] attributes

High

Links do not have a discernible name

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.

Best practices

These items highlight common accessibility best practices.

Impact

Issue

High

[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.

Best Practices

namesforever.de best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

namesforever.de SEO score

92

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

    DE

  • Language Claimed

    DE

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Namesforever.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 Namesforever.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

namesforever.de

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