Report Summary

  • 14

    Performance

    Renders faster than
    26% of other websites

  • 79

    Accessibility

    Visual factors better than
    that of 48% of websites

  • 75

    Best Practices

    More advanced features
    available than in
    36% of websites

  • 77

    SEO

    Google-friendlier than
    36% of websites

thenextsomewhere.com

The Next Somewhere Travel Blog | The Next Somewhere

Page Load Speed

12.9 sec in total

First Response

589 ms

Resources Loaded

11.6 sec

Page Rendered

709 ms

thenextsomewhere.com screenshot

About Website

Visit thenextsomewhere.com now to see the best up-to-date The Next Somewhere content and also check out these interesting facts you probably never knew about thenextsomewhere.com

The Next Somewhere is the travel, food, and lifestyle blog of Filipino-American blogger Millette Stambaugh(formerly known as Izzy Pulido) offering trip inspiration lensed through graphic design.

Visit thenextsomewhere.com

Key Findings

We analyzed Thenextsomewhere.com page load time and found that the first response time was 589 ms and then it took 12.3 sec to load all DOM resources and completely render a web page. This is a poor result, as 90% of websites can load faster.

Performance Metrics

thenextsomewhere.com performance score

14

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value10.3 s

0/100

10%

LCP (Largest Contentful Paint)

Value31.0 s

0/100

25%

SI (Speed Index)

Value44.2 s

0/100

10%

TBT (Total Blocking Time)

Value88,590 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.092

91/100

15%

TTI (Time to Interactive)

Value122.3 s

0/100

10%

Network Requests Diagram

thenextsomewhere.com

589 ms

thenextsomewhere.com

1625 ms

wp-emoji-release.min.js

69 ms

blocks.style.build.css

62 ms

sbi-styles.min.css

99 ms

Our browser made a total of 202 requests to load all elements on the main page. We found that 63% of them (128 requests) were addressed to the original Thenextsomewhere.com, 7% (15 requests) were made to Fonts.gstatic.com and 6% (13 requests) were made to C0.wp.com. The less responsive or slowest element that took the longest time to load (5.8 sec) belongs to the original domain Thenextsomewhere.com.

Page Optimization Overview & Recommendations

Page size can be reduced by 1.4 MB (24%)

Content Size

5.7 MB

After Optimization

4.3 MB

In fact, the total size of Thenextsomewhere.com main page is 5.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. 85% 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 3.5 MB which makes up the majority of the site volume.

HTML Optimization

-82%

Potential reduce by 163.2 kB

  • Original 199.4 kB
  • After minification 190.2 kB
  • After compression 36.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. 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 163.2 kB or 82% of the original size.

Image Optimization

-7%

Potential reduce by 232.7 kB

  • Original 3.5 MB
  • After minification 3.3 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. The Next Somewhere images are well optimized though.

JavaScript Optimization

-42%

Potential reduce by 523.0 kB

  • Original 1.3 MB
  • After minification 1.3 MB
  • After compression 734.3 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 523.0 kB or 42% of the original size.

CSS Optimization

-64%

Potential reduce by 475.8 kB

  • Original 749.2 kB
  • After minification 734.8 kB
  • After compression 273.4 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. Thenextsomewhere.com needs all CSS files to be minified and compressed as it can save up to 475.8 kB or 64% of the original size.

Requests Breakdown

Number of requests can be reduced by 99 (56%)

Requests Now

176

After Optimization

77

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

Accessibility Review

thenextsomewhere.com accessibility score

79

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

Low

No form fields have multiple labels

High

<frame> or <iframe> elements do not have a title

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

Best Practices

thenextsomewhere.com best practices score

75

Areas of Improvement

Trust and Safety

Impact

Issue

High

Does not use HTTPS

High

Includes front-end JavaScript libraries with known security vulnerabilities

Low

Ensure CSP is effective against XSS attacks

User Experience

Impact

Issue

High

Displays images with incorrect aspect ratio

General

Impact

Issue

Low

Detected JavaScript libraries

High

Page has valid source maps

SEO Factors

thenextsomewhere.com SEO score

77

Search Engine Optimization Advices

Crawling and Indexing

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

Impact

Issue

High

Links are not crawlable

High

robots.txt is not valid

Content Best Practices

Format your HTML in a way that enables crawlers to better understand your app’s content.

Impact

Issue

High

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

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 Thenextsomewhere.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 Thenextsomewhere.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 The Next Somewhere. This is the best way to make the web page social media friendly. Here is how it looks like on Facebook: