Report Summary

  • 15

    Performance

    Renders faster than
    27% of other websites

  • 77

    Accessibility

    Visual factors better than
    that of 44% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    55% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

somewhereweknow.com

Cultural Tours in Greece | Travel Safely | Incoming Tour Operator | Somewhere We Know

Page Load Speed

22.6 sec in total

First Response

432 ms

Resources Loaded

21.1 sec

Page Rendered

1.1 sec

somewhereweknow.com screenshot

About Website

Welcome to somewhereweknow.com homepage info - get ready to check Somewhere We Know best content right away, or after learning these important things about somewhereweknow.com

Cultural Tours in Greece - Incoming Tour Operator Greece - culinary trips - hiking trips - family trips - food & wine trips - Cultural trips Greece

Visit somewhereweknow.com

Key Findings

We analyzed Somewhereweknow.com page load time and found that the first response time was 432 ms and then it took 22.1 sec to load all DOM resources and completely render a web page. This is a poor result, as 95% of websites can load faster. Unfortunately, there was 1 request timeout, which can generally increase the web page load time, as the browser stays idle while waiting for website response.

Performance Metrics

somewhereweknow.com performance score

15

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value6.1 s

3/100

10%

LCP (Largest Contentful Paint)

Value25.3 s

0/100

25%

SI (Speed Index)

Value29.0 s

0/100

10%

TBT (Total Blocking Time)

Value5,610 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.002

100/100

15%

TTI (Time to Interactive)

Value28.8 s

0/100

10%

Network Requests Diagram

somewhereweknow.com

432 ms

somewhereweknow.com

834 ms

jquery.min.js

271 ms

jquery-migrate.min.js

528 ms

revolution.tools.min.js

808 ms

Our browser made a total of 208 requests to load all elements on the main page. We found that 83% of them (173 requests) were addressed to the original Somewhereweknow.com, 8% (16 requests) were made to Fonts.gstatic.com and 2% (4 requests) were made to Bookmundi.com. The less responsive or slowest element that took the longest time to load (19.7 sec) relates to the external source Tripadvisor.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 478.1 kB (7%)

Content Size

6.7 MB

After Optimization

6.3 MB

In fact, the total size of Somewhereweknow.com main page is 6.7 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. Only a small number of websites need less resources to load. Images take 6.0 MB which makes up the majority of the site volume.

HTML Optimization

-88%

Potential reduce by 413.2 kB

  • Original 468.2 kB
  • After minification 426.7 kB
  • After compression 55.0 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 413.2 kB or 88% of the original size.

Image Optimization

-0%

Potential reduce by 22.3 kB

  • Original 6.0 MB
  • After minification 6.0 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. Somewhere We Know images are well optimized though.

JavaScript Optimization

-16%

Potential reduce by 42.3 kB

  • Original 263.3 kB
  • After minification 261.5 kB
  • After compression 221.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. It is highly recommended that all JavaScript files should be compressed and minified as it can save up to 42.3 kB or 16% of the original size.

CSS Optimization

-14%

Potential reduce by 329 B

  • Original 2.3 kB
  • After minification 2.3 kB
  • After compression 2.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. Somewhereweknow.com needs all CSS files to be minified and compressed as it can save up to 329 B or 14% of the original size.

Requests Breakdown

Number of requests can be reduced by 101 (57%)

Requests Now

178

After Optimization

77

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

Accessibility Review

somewhereweknow.com accessibility score

77

Accessibility Issues

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

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

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

High

Lists do not contain only <li> elements and script supporting elements (<script> and <template>).

High

List items (<li>) are not contained within <ul> or <ol> parent elements.

Best Practices

somewhereweknow.com best practices score

83

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

Low

Ensure CSP is effective against XSS attacks

General

Impact

Issue

Low

Detected JavaScript libraries

High

Browser errors were logged to the console

SEO Factors

somewhereweknow.com SEO score

76

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

Links do not have descriptive text

High

Image elements do not have [alt] attributes

Crawling and Indexing

To appear in search results, crawlers need access to your app.

Impact

Issue

High

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

High

Document uses legible font sizes

High

Tap targets are not sized appropriately

Language and Encoding

  • Language Detected

    EN

  • Language Claimed

    EN

  • Encoding

    UTF-8

Language claimed in HTML meta tag should match the language actually used on the web page. Otherwise Somewhereweknow.com can be misinterpreted by Google and other search engines. Our service has detected that English is used on the page, and it matches the claimed language. Our system also found out that Somewhereweknow.com 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

Open Graph data is detected on the main page of Somewhere We Know. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: