Bergsee.gr Site Title

Bergsee Immobilien GmbH

Bergsee.gr Test Results

Bergsee.gr Mobile Performance: 38/100
Quick overview:
Opportunities
These suggestions can help your page load faster. They don't directly affect the Performance score.
Eliminate render-blocking resources. Potential savings of 6,450 ms
Resources are blocking the first paint of your page. Consider delivering critical JS/CSS inline and deferring all non-critical JS/styles. Learn more.
Reduce initial server response time. Root document took 1,050 ms
Keep the server response time for the main document short because all other requests depend on it. Learn more.
Remove unused CSS. Potential savings of 81 KiB
Remove dead rules from stylesheets and defer the loading of CSS not used for above-the-fold content to reduce unnecessary bytes consumed by network activity. Learn more.
Remove unused JavaScript. Potential savings of 138 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Serve images in next-gen formats. Potential savings of 99 KiB
Image formats like JPEG 2000, JPEG XR, and WebP often provide better compression than PNG or JPEG, which means faster downloads and less data consumption. Learn more.
Minify JavaScript. Potential savings of 119 KiB
Minifying JavaScript files can reduce payload sizes and script parse time. Learn more.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Ensure text remains visible during webfont load
Leverage the font-display CSS feature to ensure text is user-visible while webfonts are loading. Learn more.
Minimize main-thread work
2.6 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
JavaScript execution time
1.0 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid chaining critical requests
15 chains found
The Critical Request Chains below show you what resources are loaded with a high priority. Consider reducing the length of chains, reducing the download size of resources, or deferring the download of unnecessary resources to improve page load. Learn more.
Avoid long main-thread tasks
9 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Keep request counts low and transfer sizes small
22 requests • 1,116 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.

Bergsee.gr Mobile SEO: 89/100
Quick overview:
Content Best Practices
Format your HTML in a way that enables crawlers to better understand your app’s content.
Document does not have a meta description
Meta descriptions may be included in search results to concisely summarize page content. Learn more.
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.
Tap targets are not sized appropriately
50% appropriately sized tap targets
Interactive elements like buttons and links should be large enough (48x48px), and have enough space around them, to be easy enough to tap without overlapping onto other elements. Learn more.

Bergsee.gr Mobile Best Practices: 86/100
Quick overview:
Trust and Safety
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Links to cross-origin destinations are unsafe
Add `rel="noopener"` or `rel="noreferrer"` to any external links to improve performance and prevent security vulnerabilities. Learn more.
Bergsee.gr Mobile Progressive Web App: 50/100
Quick overview:
Fast and reliable
`start_url` does not respond with a 200 when offline
A service worker enables your web app to be reliable in unpredictable network conditions. Learn more. No usable web app manifest found on page.
Current page does not respond with a 200 when offline
If you're building a Progressive Web App, consider using a service worker so that your app can work offline. Learn more.
Installable
Web app manifest does not meet the installability requirements
Browsers can proactively prompt users to add your app to their homescreen, which can lead to higher engagement. Learn more. Failures: No manifest was fetched.
Does not use HTTPS
1 insecure request found
All sites should be protected with HTTPS, even ones that don't handle sensitive data. This includes avoiding mixed content, where some resources are loaded over HTTP despite the initial request being servedover HTTPS. HTTPS prevents intruders from tampering with or passively listening in on the communications between your app and your users, and is a prerequisite for HTTP/2 and many new web platform APIs. Learn more.
Does not register a service worker that controls page and `start_url`
The service worker is the technology that enables your app to use many Progressive Web App features, such as offline, add to homescreen, and push notifications. Learn more.
PWA Optimized
Manifest doesn't have a maskable icon
A maskable icon ensures that the image fills the entire shape without being letterboxed when installing the app on a device. Learn more. No manifest was fetched
Does not set a theme color for the address bar.
The browser address bar can be themed to match your site. Learn more. Failures: No manifest was fetched, No `<meta name="theme-color">` tag found.
Is not configured for a custom splash screen
A themed splash screen ensures a high-quality experience when users launch your app from their homescreens. Learn more. Failures: No manifest was fetched.
Bergsee.gr Mobile Accessibility: 100/100
Quick overview:
Similar tests
www.bergsee.com
www.bergsee.net
www.bergsee.org
www.bergsee.info
www.bergsee.biz
www.bergsee.us
www.bergsee.mobi
www.ergsee.gr
www.bergsee.gr
www.vergsee.gr
www.bvergsee.gr
www.vbergsee.gr
www.gergsee.gr
www.bgergsee.gr
www.gbergsee.gr
www.hergsee.gr
www.bhergsee.gr
www.hbergsee.gr
www.nergsee.gr
www.bnergsee.gr
www.nbergsee.gr
www.brgsee.gr
www.bwrgsee.gr
www.bewrgsee.gr
www.bwergsee.gr
www.bsrgsee.gr
www.besrgsee.gr
www.bsergsee.gr
www.bdrgsee.gr
www.bedrgsee.gr
www.bdergsee.gr
www.brrgsee.gr
www.berrgsee.gr
www.brergsee.gr
www.begsee.gr
www.beegsee.gr
www.beregsee.gr
www.beergsee.gr
www.bedgsee.gr
www.berdgsee.gr
www.befgsee.gr
www.berfgsee.gr
www.befrgsee.gr
www.betgsee.gr
www.bertgsee.gr
www.betrgsee.gr
www.bersee.gr
www.berfsee.gr
www.bergfsee.gr
www.bervsee.gr
www.bergvsee.gr
www.bervgsee.gr
www.bertsee.gr
www.bergtsee.gr
www.berbsee.gr
www.bergbsee.gr
www.berbgsee.gr
www.berysee.gr
www.bergysee.gr
www.berygsee.gr
www.berhsee.gr
www.berghsee.gr
www.berhgsee.gr
www.bergee.gr
www.bergwee.gr
www.bergswee.gr
www.bergwsee.gr
www.bergeee.gr
www.bergseee.gr
www.bergesee.gr
www.bergdee.gr
www.bergsdee.gr
www.bergdsee.gr
www.bergzee.gr
www.bergszee.gr
www.bergzsee.gr
www.bergxee.gr
www.bergsxee.gr
www.bergxsee.gr
www.bergaee.gr
www.bergsaee.gr
www.bergasee.gr
www.bergse.gr
www.bergswe.gr
www.bergsewe.gr
www.bergsse.gr
www.bergsese.gr
www.bergssee.gr
www.bergsde.gr
www.bergsede.gr
www.bergsre.gr
www.bergsere.gr
www.bergsree.gr
www.bergsew.gr
www.bergseew.gr
www.bergses.gr
www.bergsees.gr
www.bergsed.gr
www.bergseed.gr
www.bergser.gr
www.bergseer.gr
Last Tested: