5.2 sec in total
401 ms
4.6 sec
161 ms
Visit phonea.de now to see the best up-to-date Phonea content for Germany and also check out these interesting facts you probably never knew about phonea.de
Sekretariatsservice und Telefonservice: ohne Grundgebühr, nur 1,50 EUR pro Anruf für Handwerker, Anwalt, Notar, Berufsbetreuer. DER kompetente und preiswerte Telefondienst ohne monatliche Grundgebühr....
Visit phonea.deWe analyzed Phonea.de page load time and found that the first response time was 401 ms and then it took 4.8 sec to load all DOM resources and completely render a web page. This is a poor result, as 70% of websites can load faster.
phonea.de performance score
name
value
score
weighting
Value6.1 s
3/100
10%
Value11.3 s
0/100
25%
Value12.6 s
3/100
10%
Value2,640 ms
4/100
30%
Value0.537
14/100
15%
Value17.3 s
4/100
10%
401 ms
368 ms
189 ms
379 ms
194 ms
Our browser made a total of 75 requests to load all elements on the main page. We found that 67% of them (50 requests) were addressed to the original Phonea.de, 9% (7 requests) were made to Fonts.googleapis.com and 4% (3 requests) were made to S.ytimg.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Phonea.de.
Page size can be reduced by 1.0 MB (51%)
2.0 MB
994.4 kB
In fact, the total size of Phonea.de main page is 2.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. 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. Javascripts take 883.7 kB which makes up the majority of the site volume.
Potential reduce by 24.3 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 8.2 kB, which is 27% 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 24.3 kB or 81% of the original size.
Potential reduce by 10.7 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. Phonea images are well optimized though.
Potential reduce by 644.8 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 644.8 kB or 73% of the original size.
Potential reduce by 365.0 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. Phonea.de needs all CSS files to be minified and compressed as it can save up to 365.0 kB or 84% of the original size.
Number of requests can be reduced by 46 (66%)
70
24
The browser has sent 70 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Phonea. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 35 to 1 for JavaScripts and from 13 to 1 for CSS and as a result speed up the page load time.
phonea.de
401 ms
bootstrap.css
368 ms
bootstrap-responsive.css
189 ms
docs.css
379 ms
prettify.css
194 ms
prettyPhoto.css
281 ms
css
22 ms
css
33 ms
css
44 ms
css
42 ms
css
45 ms
css
46 ms
css
50 ms
logo.png
191 ms
jquery.js
16 ms
widgets.js
90 ms
jquery.js
3936 ms
prettify.js
200 ms
bootstrap-transition.js
198 ms
bootstrap-alert.js
306 ms
bootstrap-modal.js
306 ms
bootstrap-dropdown.js
351 ms
bootstrap-scrollspy.js
375 ms
bootstrap-tab.js
384 ms
bootstrap-tooltip.js
382 ms
bootstrap-popover.js
386 ms
bootstrap-button.js
386 ms
bootstrap-collapse.js
467 ms
bootstrap-carousel.js
490 ms
bootstrap-typeahead.js
491 ms
jquery.easing.1.3.js
489 ms
jquery.slabtext.min.js
488 ms
jquery.flexslider-min.js
3926 ms
superfish.js
3926 ms
plugin.js
3926 ms
jquery.prettyPhoto.js
3947 ms
twitter.js
3924 ms
js
18 ms
jquery.gmap.min.js
3925 ms
jquery.preloader.js
3955 ms
custom.js
3956 ms
atrk.js
59 ms
glyphicons-halflings.png
3697 ms
spinner.gif
3698 ms
slide_telefonservice.jpg
3698 ms
slide_empfang.jpg
3701 ms
slide_geschaeftsadresse.jpg
3702 ms
slide_faxloesungen.jpg
3702 ms
slide_phonea.jpg
3700 ms
funktion1_logo.png
3696 ms
funktion2_logo.png
3698 ms
funktion3_logo.png
3698 ms
glyphicons-halflings-white.png
3699 ms
logo-footer.png
3701 ms
H_Ihe6L3N4A
119 ms
atrk.gif
31 ms
test.png
51 ms
www-embed-player-vflfNyN_r.css
43 ms
www-embed-player.js
66 ms
base.js
3395 ms
Lrq7Jibxdtv2QOPyDSqncpDfQFNs3PE6SoUrUNh2GTU.js
84 ms
ad_status.js
83 ms
common.js
68 ms
util.js
86 ms
geocoder.js
84 ms
62 ms
arrows.png
109 ms
spinner.gif
107 ms
zN7GBFwfMP4uA6AR0HCoLQ.ttf
38 ms
RxZJdnzeo3R5zSexge8UUaCWcynf_cDxXwCLxiixG1c.ttf
39 ms
prev.png
101 ms
next.png
96 ms
bullet-hover.png
100 ms
bullet.png
100 ms
pause.png
101 ms
phonea.de accessibility score
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
[role]s are not contained by their required parent element
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
Buttons do not have an accessible name
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
phonea.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Ensure CSP is effective against XSS attacks
User Experience
Impact
Issue
Displays images with incorrect aspect ratio
General
Impact
Issue
Detected JavaScript libraries
Missing source maps for large first-party JavaScript
phonea.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
ISO-8859-15
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Phonea.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 Phonea.de main page’s claimed encoding is iso-8859-15. Changing it to UTF-8 can be a good choice, as this format is commonly used for encoding all over the web and thus their visitors won’t have any troubles with symbol transcription or reading.
phonea.de
Open Graph description is not detected on the main page of Phonea. 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: