Tools & Wizards About Us
phoneparts.de screenshot

Report Summary

  • 25

    Performance

    Renders faster than
    44% of other websites

  • 66

    Accessibility

    Visual factors better than
    that of 31% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    35% of websites

  • 83

    SEO

    Google-friendlier than
    46% of websites

phoneparts.de

Wholesale for mobile communication Accessories | B2B Großhändler für Mobilfunkzubehör

Page Load Speed

11.9 sec in total

First Response

254 ms

Resources Loaded

3.4 sec

Page Rendered

8.2 sec

phoneparts.de screenshot

About Website

Click here to check amazing Phoneparts content. Otherwise, check out these important facts you probably never knew about phoneparts.de

All about watersports, sportswear and fashion. Extensive product range including several trendy products. Fast shipping.

Visit phoneparts.de

Key Findings

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

Performance Metrics

phoneparts.de performance score

25

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value4.2 s

19/100

10%

LCP (Largest Contentful Paint)

Value5.0 s

26/100

25%

SI (Speed Index)

Value13.4 s

2/100

10%

TBT (Total Blocking Time)

Value1,650 ms

11/100

30%

CLS (Cumulative Layout Shift)

Value0.118

85/100

15%

TTI (Time to Interactive)

Value19.1 s

3/100

10%

Network Requests Diagram

phoneparts.de

254 ms

www.phonetastik.de

499 ms

phonetastik.de

549 ms

018a84afb02572e6948d78a67724eadb

119 ms

home

237 ms

Our browser made a total of 65 requests to load all elements on the main page. We found that 2% of them (1 request) were addressed to the original Phoneparts.de, 74% (48 requests) were made to Phonetastik.de and 11% (7 requests) were made to Static.hsappstatic.net. The less responsive or slowest element that took the longest time to load (1.3 sec) relates to the external source Phonetastik.de.

Page Optimization Overview & Recommendations

Page size can be reduced by 298.6 kB (4%)

Content Size

7.0 MB

After Optimization

6.7 MB

  • HTML
  • Images
  • JavaScript
  • CSS

In fact, the total size of Phoneparts.de main page is 7.0 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. 60% of websites need less resources to load. Images take 5.8 MB which makes up the majority of the site volume.

HTML Optimization

-90%

Potential reduce by 149.8 kB

  • Original 167.2 kB
  • After minification 78.1 kB
  • After compression 17.4 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 89.1 kB, which is 53% 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 149.8 kB or 90% of the original size.

Image Optimization

-2%

Potential reduce by 141.1 kB

  • Original 5.8 MB
  • After minification 5.7 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. Phoneparts images are well optimized though.

JavaScript Optimization

-1%

Potential reduce by 7.3 kB

  • Original 770.4 kB
  • After minification 770.4 kB
  • After compression 763.1 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. This website has mostly compressed JavaScripts.

CSS Optimization

-0%

Potential reduce by 335 B

  • Original 260.4 kB
  • After minification 260.4 kB
  • After compression 260.1 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. Phoneparts.de has all CSS files already compressed.

Requests Breakdown

Number of requests can be reduced by 13 (26%)

Requests Now

50

After Optimization

37

  • AJAX
  • Images
  • JavaScript
  • CSS

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

Network Requests Diagram

phoneparts.de

phoneparts.de

254 ms

www.phonetastik.de

www.phonetastik.de

499 ms

phonetastik.de

phonetastik.de

549 ms

018a84afb02572e6948d78a67724eadb

018a84afb02572e6948d78a67724eadb

119 ms

home

home

237 ms

all.css

all.css

387 ms

26778147.js

26778147.js

481 ms

all.js

all.js

671 ms

MeetingsEmbedCode.js

MeetingsEmbedCode.js

43 ms

logo-white-phonetastik.png

logo-white-phonetastik.png

100 ms

category-ersatzteile-phonetastik.jpg

category-ersatzteile-phonetastik.jpg

191 ms

Rectangle%20267@2x_(1).png

Rectangle%20267@2x_(1).png

665 ms

Rectangle%20267@2x.png

Rectangle%20267@2x.png

666 ms

Rectangle%20267@2x_(2).png

Rectangle%20267@2x_(2).png

288 ms

Vector%20%28Stroke%29.svg

Vector%20%28Stroke%29.svg

287 ms

Group%20823_%281%29.svg

Group%20823_%281%29.svg

289 ms

Group.svg

Group.svg

339 ms

Group%20823%20%281%29_%281%29.svg

Group%20823%20%281%29_%281%29.svg

383 ms

Rectangle%20249.png

Rectangle%20249.png

384 ms

Rectangle%20250.png

Rectangle%20250.png

587 ms

Rectangle%20251%20(1).png

Rectangle%20251%20(1).png

433 ms

Rectangle%20252.png

Rectangle%20252.png

765 ms

image%204_%281%29.png

image%204_%281%29.png

477 ms

image%205_%281%29.png

image%205_%281%29.png

530 ms

image%202_%281%29.png

image%202_%281%29.png

585 ms

image%203_%281%29.png

image%203_%281%29.png

624 ms

pngwing%201_%281%29.png

pngwing%201_%281%29.png

667 ms

MicrosoftTeams-image.jpg

MicrosoftTeams-image.jpg

765 ms

g981.svg

g981.svg

720 ms

Vector.svg

Vector.svg

760 ms

Vector%20%28Stroke%29%20%281%29.svg

Vector%20%28Stroke%29%20%281%29.svg

762 ms

landingpage-blured-bg.svg

landingpage-blured-bg.svg

762 ms

Vector%20%281%29.svg

Vector%20%281%29.svg

814 ms

icon.svg

icon.svg

854 ms

Vector%20%282%29.svg

Vector%20%282%29.svg

856 ms

Vector%20%283%29.svg

Vector%20%283%29.svg

858 ms

12.jpg

12.jpg

1146 ms

20230417_155159.jpg

20230417_155159.jpg

1270 ms

Ellipseone.png

Ellipseone.png

910 ms

AYE.png

AYE.png

949 ms

phonetastik-logo.png

phonetastik-logo.png

950 ms

Design%20ohne%20Titel%20(10).png

Design%20ohne%20Titel%20(10).png

951 ms

Inter-Regular.ttf

Inter-Regular.ttf

1045 ms

Inter-Medium.ttf

Inter-Medium.ttf

1084 ms

26778147.js

26778147.js

493 ms

banner.js

banner.js

484 ms

web-interactives-embed.js

web-interactives-embed.js

478 ms

fb.js

fb.js

418 ms

collectedforms.js

collectedforms.js

485 ms

conversations-embed.js

conversations-embed.js

452 ms

onboarding-service

onboarding-service

457 ms

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

PAJJhLM6sSoWKfWCAAwDAjgbRAAB42mNgYGBkAIIbCZo5IPrmUn0hGA0AO8EFTQAA

22 ms

Inter-Light.ttf

Inter-Light.ttf

1041 ms

Inter-ExtraLight.ttf

Inter-ExtraLight.ttf

957 ms

Inter-Thin.ttf

Inter-Thin.ttf

955 ms

Inter-SemiBold.ttf

Inter-SemiBold.ttf

951 ms

Inter-Bold.ttf

Inter-Bold.ttf

982 ms

Inter-ExtraBold.ttf

Inter-ExtraBold.ttf

981 ms

Inter-Black.ttf

Inter-Black.ttf

931 ms

bundle.production.js

bundle.production.js

17 ms

configure-monitoring-eu1.js

configure-monitoring-eu1.js

19 ms

book-info-early-requester.js

book-info-early-requester.js

59 ms

project_with_deps.css

project_with_deps.css

26 ms

bundle.production.js

bundle.production.js

21 ms

project.js

project.js

39 ms

Accessibility Review

phoneparts.de accessibility score

66

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-*] attributes do not match their roles

High

Elements with an ARIA [role] that require children to contain a specific [role] are missing some or all of those required children.

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.

Navigation

These are opportunities to improve keyboard navigation in your application.

Impact

Issue

High

Heading elements are not in a sequentially-descending order

Best Practices

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

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

High

Missing source maps for large first-party JavaScript

SEO Factors

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

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 Phoneparts.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 Phoneparts.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

phoneparts.de

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