Sees.ee Site Title

SEES

Sees.ee Meta Description

SEES is an Interior Architecture studio that celebrates elegant, simple, comfortable and durable designs. Our refined palette of modern and natural materials and textures create interiors, which seek to celebrate the experience of space and life within it.

Sees.ee Test Results

Sees.ee Mobile Performance: 18/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 5,110 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.
Serve images in next-gen formats. Potential savings of 891 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.
Properly size images. Potential savings of 500 KiB
Serve images that are appropriately-sized to save cellular data and improve load time. Learn more.
Efficiently encode images. Potential savings of 454 KiB
Optimized images load faster and consume less cellular data. Learn more.
Remove unused JavaScript. Potential savings of 280 KiB
Remove unused JavaScript to reduce bytes consumed by network activity. Learn more.
Remove unused CSS. Potential savings of 53 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.
Diagnostics
More information about the performance of your application. These numbers don't directly affect the Performance score.
Reduce the impact of third-party code
Third-party code blocked the main thread for 1,490 ms
Third-party code can significantly impact load performance. Limit the number of redundant third-party providers and try to load third-party code after your page has primarily finished loading. Learn more.
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
5.7 s
Consider reducing the time spent parsing, compiling and executing JS. You may find delivering smaller JS payloads helps with this. Learn more
Serve static assets with an efficient cache policy
21 resources found
A long cache lifetime can speed up repeat visits to your page. Learn more.
Reduce JavaScript execution time
3.3 s
Consider reducing the time spent parsing, compiling, and executing JS. You may find delivering smaller JS payloads helps with this. Learn more.
Keep request counts low and transfer sizes small
40 requests • 2,313 KiB
To set budgets for the quantity and size of page resources, add a budget.json file. Learn more.
Largest Contentful Paint element
1 element found
This is the largest contentful element painted within the viewport. Learn More
Avoid long main-thread tasks
10 long tasks found
Lists the longest tasks on the main thread, useful for identifying worst contributors to input delay. Learn more
Avoid chaining critical requests
13 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 large layout shifts
3 elements found
These DOM elements contribute most to the CLS of the page.

Sees.ee Mobile SEO: 100/100
Quick overview:

Sees.ee Mobile Best Practices: 86/100
Quick overview:
Trust and Safety
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.
Does not use HTTPS
12 insecure requests 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.
Sees.ee Mobile Progressive Web App: 39/100
Quick overview:
PWA Optimized
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.
Does not redirect HTTP traffic to HTTPS
If you've already set up HTTPS, make sure that you redirect all HTTP traffic to HTTPS in order to enable secure web features for all your users. Learn more.
Does not provide a valid `apple-touch-icon`
For ideal appearance on iOS when users add a progressive web app to the home screen, define an `apple-touch-icon`. It must point to a non-transparent 192px (or 180px) square PNG. Learn More.
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.
Fast and reliable
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.
`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.
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 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.
Does not use HTTPS
12 insecure requests 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.
Sees.ee Mobile Accessibility: 98/100
Quick overview:
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.
Links do not have a discernible name
Link text (and alternate text for images, when used as links) that is discernible, unique, and focusable improves the navigation experience for screen reader users. Learn more.
Similar tests
www.sees.com
www.sees.net
www.sees.org
www.sees.info
www.sees.biz
www.sees.us
www.sees.mobi
www.ees.ee
www.sees.ee
www.wees.ee
www.swees.ee
www.wsees.ee
www.eees.ee
www.seees.ee
www.esees.ee
www.dees.ee
www.sdees.ee
www.dsees.ee
www.zees.ee
www.szees.ee
www.zsees.ee
www.xees.ee
www.sxees.ee
www.xsees.ee
www.aees.ee
www.saees.ee
www.asees.ee
www.ses.ee
www.swes.ee
www.sewes.ee
www.sses.ee
www.seses.ee
www.ssees.ee
www.sdes.ee
www.sedes.ee
www.sres.ee
www.seres.ee
www.srees.ee
www.sews.ee
www.seews.ee
www.sess.ee
www.seess.ee
www.seds.ee
www.seeds.ee
www.sers.ee
www.seers.ee
www.see.ee
www.seew.ee
www.seesw.ee
www.seee.ee
www.seese.ee
www.seed.ee
www.seesd.ee
www.seez.ee
www.seesz.ee
www.seezs.ee
www.seex.ee
www.seesx.ee
www.seexs.ee
www.seea.ee
www.seesa.ee
www.seeas.ee
Last Tested: