Report Summary

  • 16

    Performance

    Renders faster than
    30% of other websites

  • 75

    Accessibility

    Visual factors better than
    that of 42% of websites

  • 83

    Best Practices

    More advanced features
    available than in
    56% of websites

  • 76

    SEO

    Google-friendlier than
    35% of websites

fodors.biz

Fodors Travel Guide – Plan Your Trip Online

Page Load Speed

21.9 sec in total

First Response

362 ms

Resources Loaded

20.9 sec

Page Rendered

721 ms

fodors.biz screenshot

About Website

Visit fodors.biz now to see the best up-to-date Fodors content for United States and also check out these interesting facts you probably never knew about fodors.biz

Fodor's provides expert travel content worth exploring so you can dream up your next trip. The world is a weird and wonderful place—we want to show you around.

Visit fodors.biz

Key Findings

We analyzed Fodors.biz page load time and found that the first response time was 362 ms and then it took 21.6 sec to load all DOM resources and completely render a web page. This is an excellent result, as only a small number 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

fodors.biz performance score

16

Measured Metrics

name

value

score

weighting

FCP (First Contentful Paint)

Value5.4 s

6/100

10%

LCP (Largest Contentful Paint)

Value9.0 s

1/100

25%

SI (Speed Index)

Value16.9 s

0/100

10%

TBT (Total Blocking Time)

Value7,410 ms

0/100

30%

CLS (Cumulative Layout Shift)

Value0.013

100/100

15%

TTI (Time to Interactive)

Value39.4 s

0/100

10%

Network Requests Diagram

www.fodors.com

362 ms

analytics.js

37 ms

all.ib.travel.js

20374 ms

morpheus.ibtravel.2487.js

27 ms

184397-210395096453378.js

27 ms

Our browser made a total of 179 requests to load all elements on the main page. We found that 0% of them (0 request) were addressed to the original Fodors.biz, 12% (21 requests) were made to S0.2mdn.net and 7% (12 requests) were made to Fodors.com. The less responsive or slowest element that took the longest time to load (20.4 sec) relates to the external source Cdn.districtm.ca.

Page Optimization Overview & Recommendations

Page size can be reduced by 2.9 MB (45%)

Content Size

6.6 MB

After Optimization

3.6 MB

In fact, the total size of Fodors.biz main page is 6.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 3.6 MB which makes up the majority of the site volume.

HTML Optimization

-80%

Potential reduce by 175.4 kB

  • Original 218.6 kB
  • After minification 209.1 kB
  • After compression 43.2 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 175.4 kB or 80% of the original size.

Image Optimization

-25%

Potential reduce by 894.9 kB

  • Original 3.6 MB
  • After minification 2.7 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. Obviously, Fodors needs image optimization as it can save up to 894.9 kB or 25% of the original volume. The most popular and efficient tools for JPEG and PNG image optimization are Jpegoptim and PNG Crush.

JavaScript Optimization

-63%

Potential reduce by 1.4 MB

  • Original 2.2 MB
  • After minification 2.2 MB
  • After compression 840.0 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 1.4 MB or 63% of the original size.

CSS Optimization

-87%

Potential reduce by 472.8 kB

  • Original 541.7 kB
  • After minification 539.2 kB
  • After compression 68.9 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. Fodors.biz needs all CSS files to be minified and compressed as it can save up to 472.8 kB or 87% of the original size.

Requests Breakdown

Number of requests can be reduced by 92 (58%)

Requests Now

160

After Optimization

68

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

Accessibility Review

fodors.biz accessibility score

75

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.

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

High

ARIA IDs are not unique

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>).

Best Practices

fodors.biz 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

High

Missing source maps for large first-party JavaScript

SEO Factors

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