15 sec in total
531 ms
13.4 sec
997 ms
Click here to check amazing Portal Hamburg content. Otherwise, check out these important facts you probably never knew about portalhamburg.de
Portal Hamburg I❶I Die Info Webseiten der Hansestadt seit 2007 - Suchen & Finden Sie in 250 Kategorien das Richtige ✓ Alle Branchen
Visit portalhamburg.deWe analyzed Portalhamburg.de page load time and found that the first response time was 531 ms and then it took 14.4 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.
portalhamburg.de performance score
name
value
score
weighting
Value6.4 s
2/100
10%
Value14.7 s
0/100
25%
Value14.2 s
1/100
10%
Value690 ms
43/100
30%
Value1.177
1/100
15%
Value16.6 s
5/100
10%
531 ms
315 ms
300 ms
302 ms
395 ms
Our browser made a total of 127 requests to load all elements on the main page. We found that 49% of them (62 requests) were addressed to the original Portalhamburg.de, 38% (48 requests) were made to Maps.googleapis.com and 6% (7 requests) were made to Fonts.gstatic.com. The less responsive or slowest element that took the longest time to load (4 sec) belongs to the original domain Portalhamburg.de.
Page size can be reduced by 272.2 kB (17%)
1.6 MB
1.3 MB
In fact, the total size of Portalhamburg.de main page is 1.6 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. 80% 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 984.6 kB which makes up the majority of the site volume.
Potential reduce by 250.7 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 250.7 kB or 89% of the original size.
Potential reduce by 19.6 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. Portal Hamburg images are well optimized though.
Potential reduce by 1.2 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.
Potential reduce by 633 B
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. Portalhamburg.de has all CSS files already compressed.
Number of requests can be reduced by 70 (60%)
116
46
The browser has sent 116 CSS, Javascripts, AJAX and image requests in order to completely render the main page of Portal Hamburg. We recommend that multiple CSS and JavaScript files should be merged into one by each type, as it can help reduce assets requests from 43 to 1 for JavaScripts and from 17 to 1 for CSS and as a result speed up the page load time.
portalhamburg.de
531 ms
fpwn5.css
315 ms
fpwn4.css
300 ms
fpwn4.css
302 ms
fpwn4.css
395 ms
post-3885.css
333 ms
fpwn4.css
326 ms
post-3633.css
414 ms
fpwn4.css
410 ms
icon
27 ms
fpwn4.css
436 ms
fpwn4.css
434 ms
css
40 ms
fpwn5.js
548 ms
fq0kt.css
429 ms
fpwn4.css
428 ms
regenerator-runtime.min.js
431 ms
wp-polyfill.min.js
447 ms
index.js
611 ms
jquery.blockUI.min.js
611 ms
add-to-cart.min.js
612 ms
js.cookie.min.js
611 ms
woocommerce.min.js
613 ms
cart-fragments.min.js
614 ms
js
67 ms
google-maps.js
638 ms
core.min.js
692 ms
mouse.min.js
691 ms
sortable.min.js
692 ms
moment.min.js
697 ms
de.min.js
32 ms
select2.js
750 ms
vue.min.js
760 ms
slider.min.js
768 ms
vendor.js
853 ms
frontend.js
784 ms
webpack.runtime.min.js
784 ms
frontend-modules.min.js
865 ms
waypoints.min.js
866 ms
swiper.min.js
1018 ms
share-link.min.js
1014 ms
dialog.min.js
815 ms
frontend.min.js
810 ms
preloaded-modules.min.js
791 ms
2.jpg
273 ms
hamburg-3846525_1920.jpg
519 ms
August-2019-128-1024x664.jpg
674 ms
011-1024x433.jpg
670 ms
tick.svg
473 ms
IMG_3655-768x444.jpg
674 ms
capture-20190422-112426-150x74.png
519 ms
Slideshow_Shop-768x512.jpg
675 ms
IMG_2378-150x150.png
673 ms
Fassadenmarkisen_KLAIBER_Ventosol_VS5200_002-1024x819-1-768x381.jpg
752 ms
cropped-Icon-150x150.png
673 ms
Unterglasmarkise_VARISOL-Unterglasmarkise-T100-3.jpg
675 ms
Unterglasmarkise_VARISOL-Unterglasmarkise-T100-3-150x150.jpg
693 ms
171006-CA2_5392-Wellingsb%E2%94%9C%E2%95%9Dttler-Landstra%E2%94%9C%C6%92e-59-Hamburg-%E2%94%AC%C2%AE-LM-M%E2%94%9C%E2%95%9Dller-F1-HDR-1-1024x682-1-768x512.jpg
692 ms
capture-20210128-135932-150x76.png
693 ms
P1000297-768x512.jpg
693 ms
PHOTO-2020-01-14-20-150x150.jpg
734 ms
capture-20191021-085646-768x407.jpg
816 ms
flUhRq6tzZclQEJ-Vdg-IuiaDsNZIhQ8tQ.ttf
77 ms
icomoon.ttf
817 ms
fontawesome-webfont.woff
915 ms
gen_204
76 ms
common.js
81 ms
util.js
97 ms
geocoder.js
80 ms
portalhamburg.de
3954 ms
map.js
136 ms
portalhamburg.de
4048 ms
overlay.js
134 ms
stats.js
132 ms
controls.js
132 ms
places_impl.js
132 ms
openhand_8_8.cur
181 ms
onion.js
93 ms
powered-by-google-on-white3.png
135 ms
autocomplete-icons.png
273 ms
ViewportInfoService.GetViewportInfo
207 ms
KFOmCnqEu92Fr1Mu4mxPKTU1Kg.ttf
158 ms
KFOlCnqEu92Fr1MmEU9fBBc9AMP6lQ.ttf
207 ms
KFOlCnqEu92Fr1MmSU5fBBc9AMP6lQ.ttf
207 ms
KFOkCnqEu92Fr1MmgVxIIzcXKMny.ttf
209 ms
KFOlCnqEu92Fr1MmWUlfBBc9AMP6lQ.ttf
207 ms
KFOlCnqEu92Fr1MmYUtfBBc9AMP6lQ.ttf
207 ms
AuthenticationService.Authenticate
80 ms
vt
19 ms
vt
18 ms
vt
20 ms
vt
24 ms
vt
28 ms
vt
34 ms
vt
44 ms
vt
43 ms
vt
50 ms
vt
51 ms
vt
53 ms
vt
61 ms
vt
64 ms
vt
63 ms
vt
71 ms
vt
70 ms
vt
72 ms
vt
80 ms
vt
79 ms
vt
84 ms
vt
143 ms
vt
144 ms
vt
146 ms
vt
149 ms
vt
146 ms
vt
144 ms
vt
146 ms
vt
147 ms
vt
148 ms
vt
149 ms
vt
152 ms
vt
154 ms
vt
163 ms
vt
146 ms
QuotaService.RecordEvent
157 ms
transparent.png
149 ms
css
68 ms
css
69 ms
fpwn4.css
107 ms
portalhamburg.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
ARIA input fields do not have accessible names
Contrast
These are opportunities to improve the legibility of your content.
Impact
Issue
Background and foreground colors do not have a sufficient contrast ratio.
Navigation
These are opportunities to improve keyboard navigation in your application.
Impact
Issue
Heading elements are not in a sequentially-descending order
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
Image elements do not have [alt] attributes
Form elements do not have associated labels
Links do not have a discernible name
Tables and lists
These are opportunities to improve the experience of reading tabular or list data using assistive technology, like a screen reader.
Impact
Issue
List items (<li>) are not contained within <ul> or <ol> parent elements.
Best practices
These items highlight common accessibility best practices.
Impact
Issue
[user-scalable="no"] is used in the <meta name="viewport"> element or the [maximum-scale] attribute is less than 5.
portalhamburg.de best practices score
Trust and Safety
Impact
Issue
Does not use HTTPS
Includes front-end JavaScript libraries with known security vulnerabilities
Ensure CSP is effective against XSS attacks
General
Impact
Issue
Detected JavaScript libraries
Issues were logged in the Issues panel in Chrome Devtools
portalhamburg.de SEO score
Crawling and Indexing
To appear in search results, crawlers need access to your app.
Impact
Issue
Links are not crawlable
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Impact
Issue
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
Document uses legible font sizes
Tap targets are not sized appropriately
DE
DE
UTF-8
Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Portalhamburg.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 Portalhamburg.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.
portalhamburg.de
Open Graph data is detected on the main page of Portal Hamburg. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: